Todd Greenwood-Geer commented on ZOOKEEPER-498:

Thanks for the update. I'm closely following the dev alias and 
appreciate the effort the ZK team is putting in. For the time being, 
I'll stick with 3.1.1 and solve our WAN issues with an ensemble 

I'm in the middle of writing that bit right now.

BTW - Should I succeed in convincing my company to allow me to open 
source various components that I've written (on top of zookeeper), what 
is the process for that?


> 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, ZOOKEEPER-498.patch, 
> 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