]
Wolf-Dieter Fink commented on ISPN-12224:
-----------------------------------------
As discussed the behavior should be to reject client access and do no rebalancing until
all the former known cluster nodes are back and ready (might be loaded from persistence).
After this there is no need for rebalancing as the state and data distribution is the same
as before.
From now on the cluster will act as normal and up- downscaling is possible and will
trigger a rebalancing
Cluster in a confusing state after restarted from graceful shutdown -
no hint for waiting on complete restarted
---------------------------------------------------------------------------------------------------------------
Key: ISPN-12224
URL:
https://issues.redhat.com/browse/ISPN-12224
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 12.0.0.Dev01, 11.0.3.Final
Reporter: Wolf-Dieter Fink
Priority: Critical
After a cluster is stopped with "shutdown cluster" and incomplete restart there
is no WARN or INFO message that the cluster is in an incomplete state if not all nodes are
back.
If there is a single node started it is still possible to add new entries!!
As well as entries can be read.
But the server will throw Exceptions.
The expectation is to have log messages with a statement that the cluster of (a,b, ...)
is incomplete started after graceful shutdown and the missing nodes are (x,y,...)
It should not be possible to access caches.
There should be a CLI/JMX option to interrupt the graceful start and set the cluster to a
working state - even if there is a possible loss of data in this case.