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

Posted to dev@zookeeper.apache.org by "Jeffrey F. Lukman (JIRA)" <ji...@apache.org> on 2017/08/04 20:54:00 UTC

[jira] [Created] (ZOOKEEPER-2865) Reconfig Causes Inconsistent Configuration file among the nodes

Jeffrey F. Lukman created ZOOKEEPER-2865:
--------------------------------------------

             Summary: Reconfig Causes Inconsistent Configuration file among the nodes
                 Key: ZOOKEEPER-2865
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2865
             Project: ZooKeeper
          Issue Type: Bug
          Components: leaderElection, quorum, server
    Affects Versions: 3.5.3
            Reporter: Jeffrey F. Lukman


When we run our Distributed system Model Checking (DMCK) in ZooKeeper v3.5.3
by following the workload in ZK-2778:
- initially start 2 ZooKeeper nodes
- start 3 new nodes
- do a reconfiguration (the complete reconfiguration is attached in the document)

We think our DMCK found this following bug:
- while one of the just joined nodes has not received the latest configuration update ~ called as node X ~ the initial leader node closed its port, therefore causing the node X to be isolated.

For complete information of the bug, please see the document that is attached.





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