Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-2865

Reconfig Causes Inconsistent Configuration file among the nodes

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Trivial
    • Resolution: Fixed
    • 3.5.3
    • 3.5.4, 3.6.0
    • documentation
    • None

    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.

      Attachments

        1. ZK-2865.pdf
          130 kB
          Jeffrey F. Lukman

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            shralex Alexander Shraer
            jeffreyflukman Jeffrey F. Lukman
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment