[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739796#action_12739796
 ] 

Patrick Hunt commented on ZOOKEEPER-498:
----------------------------------------

there are docs in the source code that provide good low level detail on flex 
quorum implementation

HOWEVER, there are NO docs in the Ops guide detailing user level flex quorum 
operation

we need to add docs (as part of this fix) to forrest detailing how to 
operate/troubleshoot/debug flex quorum


> 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
>
>
> 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