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

Leader election selected incorrect leader

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

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Not A Problem
    • 3.2.2
    • None
    • leaderElection, server
    • None
    • Cloudera distribution of zookeeper (patched to never cache DNS entries)
      Debian lenny

    Description

      We had three nodes running zookeeper:

      • 192.168.130.10
      • 192.168.130.11
      • 192.168.130.14

      192.168.130.11 failed, and was replaced by a new node 192.168.130.13 (automated startup). The new node had not participated in any zookeeper quorum previously. The node 192.148.130.11 was permanently removed from service and could not contribute to the quorum any further (powered off).

      DNS entries were updated for the new node to allow all the zookeeper servers to find the new node.

      The new node 192.168.130.13 was selected as the LEADER, despite the fact that it had not seen the latest zxid.

      This particular problem has not been verified with later versions of zookeeper, and no attempt has been made to reproduce this problem as yet.

      Attachments

        1. zklogs-20101102144159SAST.tar.gz
          6.12 MB
          Alexandre Hardy

        Activity

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

          People

            Unassigned Unassigned
            ahardy Alexandre Hardy
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment