Mo created IGNITE-8592:
--------------------------
Summary: Network partitions lead to two independent clusters
Key: IGNITE-8592
URL: https://issues.apache.org/jira/browse/IGNITE-8592
Project: Ignite
Issue Type: Bug
Affects Versions: 2.4
Reporter: Mo
Creating a network partition in a replicated Ignite cluster leads to creating
two independent clusters, each of which would operate independently from the
other, even after the network partition is healed.
Setup: 3 servers (s1,s2,s3) two clients (c1,c2).
A partition created \{(s1,s2,c1),(s3,c2)}.
--> At this point two independent clusters form; one containing s1 and s2,
while the other containing s3. The two never rejoin even after the partition is
healed.
This creates different kinds of problems for the different data structure
ignite provides, such as the cache (stale reads, and data unavailability),
atomic types (atomicref and long ) ... etc.
These are the settings used for the replicated cache:
cfg.setCacheMode(CacheMode.REPLICATED);
cfg.setAtomicityMode(CacheAtomicityMode.ATOMIC);
cfg.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
cfg.setReadFromBackup(false);
cfg.setPartitionLossPolicy(PartitionLossPolicy.READ_ONLY_SAFE);
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
