Mo created IGNITE-9765:
--------------------------
Summary: Network partition leads to failures in Ignite's queue
Key: IGNITE-9765
URL: https://issues.apache.org/jira/browse/IGNITE-9765
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.
Affected operations:
* *Queue add*: Inserting an element to *s3*'s queue ** will no be propagated
to *s1* and *s2* even after the partition is healed. This leads to data
unavailability.
* *Queue remove:* Removing an element from the queue in *s3* will not be
executed in the other servers. This leads to reappearance of deleted data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
