Flavio Paiva Junqueira updated ZOOKEEPER-498:

    Attachment: ZOOKEEPER-498.patch

I have generated a patch for this issue. I verified that I didn't do the 
correct checks in ZOOKEEPER-491, so I try to fix it in this patch. I have also 
modified the test to fix the problem with the fail assertion, and I have 
inspected the logs to see if it is behaving as expected. I can see no problem 
at this time with this patch.

If someone else is interested in checking it out, please do it.

> Unending Leader Elections : WAN configuration
> ---------------------------------------------
>                 Key: ZOOKEEPER-498
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-498
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: leaderElection
>    Affects Versions: 3.2.0
>         Environment: Each machine:
> CentOS 5.2 64-bit
> 2GB ram
> java version "1.6.0_13"
> Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02, mixed 
> Network Topology:
> DC : central data center
> POD(N): remote data center
> Zookeeper Topology:
> Leaders may be elected only in DC (weight = 1)
> Only followers are elected in PODS (weight = 0)
>            Reporter: Todd Greenwood-Geer
>            Assignee: Flavio Paiva Junqueira
>            Priority: Critical
>             Fix For: 3.2.1, 3.3.0
>         Attachments: dc-zook-logs-01.tar.gz, pod-zook-logs-01.tar.gz, 
> zk498-test.tar.gz, zoo.cfg, ZOOKEEPER-498.patch
> In a WAN configuration, ZooKeeper is endlessly electing, terminating, and 
> re-electing a ZooKeeper leader. The WAN configuration involves two groups, a 
> central DC group of ZK servers that have a voting weight = 1, and a group of 
> servers in remote pods with a voting weight of 0.
> What we expect to see is leaders elected only in the DC, and the pods to 
> contain only followers. What we are seeing is a continuous cycling of 
> leaders. We have seen this consistently with 3.2.0, 3.2.0 + recommended 
> patches (473, 479, 481, 491), and now release 3.2.1.

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

Reply via email to