Mo created IGNITE-9768: -------------------------- Summary: Network partition leads to failures in Ignite's atomic data types. Key: IGNITE-9768 URL: https://issues.apache.org/jira/browse/IGNITE-9768 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 leads to a faulty atomic types in Ignite. Affected data types: * *Atomic Sequence*: An IncrementAndGet operation on *s3* will no affect the sequence in both *s1* and *s2* (even after the partition is healed). * *AtomicLong* and *AtomicRef*: Operations such as IncrementAndGet, CompareAndSet on *s3* will not be reflected to *s1* and *s2* even after the partition heals, which leads in faulty results for clients connected to these servers. * *CountDownLatch*: A CountDown Operation on the latch in *s3* will not be reflected to the other servers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)