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:22:00 UTC
[jira] [Created] (IGNITE-9767) Network partition leads to failures
in Ignite's semaphore
Mo created IGNITE-9767:
--------------------------
Summary: Network partition leads to failures in Ignite's semaphore
Key: IGNITE-9767
URL: https://issues.apache.org/jira/browse/IGNITE-9767
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 semaphore on both sides of the partition. For example, if a semaphore with one permit is created in the cluster, after creating a network partition and healing it, both *c1* and *c2* can acquire that one permit.
System config:
Release acquired permits if node, that owned them, left topology ==> Set to true
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)