You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexandr Kuramshin (JIRA)" <ji...@apache.org> on 2017/09/28 07:03:00 UTC

[jira] [Created] (IGNITE-6519) Race in SplitAwareTopologyValidator on activator and server node join

Alexandr Kuramshin created IGNITE-6519:
------------------------------------------

             Summary: Race in SplitAwareTopologyValidator on activator and server node join
                 Key: IGNITE-6519
                 URL: https://issues.apache.org/jira/browse/IGNITE-6519
             Project: Ignite
          Issue Type: Bug
          Components: cache
    Affects Versions: 2.1
            Reporter: Alexandr Kuramshin
            Assignee: Alexandr Kuramshin


The following sequence may occur:

1. {{SplitAwareTopologyValidator}} detects split, gets {{NOTVALID}} and returns false from {{validate()}}

2. Activator node joins and {{SplitAwareTopologyValidator}} gets {{REPAIRED}}

3. Server node joins from other DC and it makes {{SplitAwareTopologyValidator}} gets {{VALID}}

4. Then the server node left the cluster and {{SplitAwareTopologyValidator}} should return false from {{validate()}} in cause of next split

But current implementation makes {{SplitAwareTopologyValidator}} auto-{{REPAIRED}}. Actually if the activator node will being forgotten to leave the cluster it may automatically repair a split many times. But it supposed to be manual operation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)