hadoop-zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandre Hardy (JIRA)" <j...@apache.org>
Subject [jira] Created: (ZOOKEEPER-917) Leader election selected incorrect leader
Date Wed, 03 Nov 2010 12:35:37 GMT
Leader election selected incorrect leader
-----------------------------------------

                 Key: ZOOKEEPER-917
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-917
             Project: Zookeeper
          Issue Type: Bug
          Components: leaderElection, server
    Affects Versions: 3.2.2
         Environment: Cloudera distribution of zookeeper (patched to never cache DNS entries)
Debian lenny
            Reporter: Alexandre Hardy
            Priority: Critical


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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message