[
https://issues.apache.org/jira/browse/ZOOKEEPER-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740732#action_12740732
]
Patrick Hunt commented on ZOOKEEPER-498:
----------------------------------------
I also tried this (todd's original configuration) and it also works with this
patch:
9 servers: weight 1:1:1:1:1:0:0:0:0 2 groups 1:2:3:4:5 6:7:8:9 : OK
server 1 config:
---------------------
tickTime=2000
initLimit=10
syncLimit=5
dataDir=./s1/data
clientPort=2181
electionAlg=3
server.1=localhost:3181:4181
server.2=localhost:3182:4182
server.3=localhost:3183:4183
server.4=localhost:3184:4184
server.5=localhost:3185:4185
server.6=localhost:3186:4186
server.7=localhost:3187:4187
server.8=localhost:3188:4188
server.9=localhost:3189:4189
weight.1=1
weight.2=1
weight.3=1
weight.4=1
weight.5=1
weight.6=0
weight.7=0
weight.8=0
weight.9=0
group.1=1:2:3:4:5
group.2=6:7:8:9
> 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.
