[ZOOKEEPER-2865] Reconfig Causes Inconsistent Configuration file among the nodes

• Type: Improvement
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 3.5.3
• Fix Version/s: 3.5.4, 3.6.0
• Component/s: documentation
• Assignee: Alexander Shraer
• Reporter: Jeffrey F. Lukman
• Created: 04/Aug/17 20:53
• Updated: 01/Sep/17 19:30
• Resolved: 06/Aug/17 04:22

Description

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.

Issue Links

• links to: GitHub Pull Request #328