You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Mo (JIRA)" <ji...@apache.org> on 2018/10/02 10:15:00 UTC

[jira] [Created] (IGNITE-9766) Network partition leads to failures in Ignite's set

Mo created IGNITE-9766:
--------------------------

             Summary: Network partition leads to failures in Ignite's set
                 Key: IGNITE-9766
                 URL: https://issues.apache.org/jira/browse/IGNITE-9766
             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 set in both sides of the partition. For example, adding an element to the set in *s3* will not add that element *s1* and *s2*, even after the partition is healed. This leads to data unavailability.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)