[
https://issues.jboss.org/browse/ISPN-5965?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-5965:
------------------------------------
My feeling is that the cluster would spend too much time in read-only mode, as it would
have to enter after any node crashes. But I guess the option could be useful if the cache
is mostly static and the application can tolerate stale data (as the cache could stay in
read-only mode for a very long time).
Add a new mode (READ ONLY) for Partition Handling
-------------------------------------------------
Key: ISPN-5965
URL:
https://issues.jboss.org/browse/ISPN-5965
Project: Infinispan
Issue Type: Feature Request
Components: Core
Reporter: Wolf-Dieter Fink
Labels: partition_handling
Without any PartitionHandling it is not possible to ensure the consistency of the cache.
With PH enabled it depends whether the remaining partition has the majority or at least
all owners for a particular key to be able to access the key.
In some cases the prefered behaviour is to keep every entry readable but prevent from any
change to keep consistency.
So there should be a configuration option for the partition handling to switch all
instances to READ_ONLY instead of AVAILABLE/DEGRADED.
In this case each get will return the current value but each put will be rejected with a
AvailabilityException
This prevents from any rebalancing if one partition contains a majority and stay
available.
But in case of a real instance crash it might need a human interaction to set the state
back to AVAILABLE as the node will never come back to the cluster.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)