[infinispan-issues] [JBoss JIRA] (ISPN-5511) Add a read-only mode for caches during split-brain with partition handling enabled
Wolf-Dieter Fink (JIRA)
issues at jboss.org
Tue May 26 11:00:06 EDT 2015
[ https://issues.jboss.org/browse/ISPN-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wolf-Dieter Fink updated ISPN-5511:
-----------------------------------
Description:
If a split-brain happen and PH is enabled it would be worth in some use-cases that the complete cache becomes read-only instead of having some keys (DIST) or a complete instance (REPL) unavailable.
so a configuration like
<partitionHandling enabled="true" read-only="true" />
where read-only=false is the default to have the same behaviour as before might cover such cases.
It seems to be worth for DIST and REPL caches.
was:
If a split-brain happen and PH is enabled it would be worth in some use-cases that the complete cache becomes read-only instead of having some keys (DIST) or a complete instance (REPL) unavailable.
so a configuration like
<partitionHandling enabled="true" read-only="true" />
where read-only=false is the default to have the same behaviour as before might cover such cases
> Add a read-only mode for caches during split-brain with partition handling enabled
> ----------------------------------------------------------------------------------
>
> Key: ISPN-5511
> URL: https://issues.jboss.org/browse/ISPN-5511
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Reporter: Wolf-Dieter Fink
> Labels: partition_handling
>
> If a split-brain happen and PH is enabled it would be worth in some use-cases that the complete cache becomes read-only instead of having some keys (DIST) or a complete instance (REPL) unavailable.
> so a configuration like
> <partitionHandling enabled="true" read-only="true" />
> where read-only=false is the default to have the same behaviour as before might cover such cases.
> It seems to be worth for DIST and REPL caches.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the infinispan-issues
mailing list