Mohammad Etemad created ZOOKEEPER-2986:
------------------------------------------
Summary: My id not in the peer list
Key: ZOOKEEPER-2986
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2986
Project: ZooKeeper
Issue Type: Bug
Environment: Running in a docker container in kubernetes 1.5
Reporter: Mohammad Etemad
Zookeeper 3.5.3-beta is throwing the following error. I am facing the issue of
"My id 1 not in the peer list". If I use the alpha version (3.5.2) and then
upgrade to the 3.5.3 beta version, the problem goes away. But if I implement
the 3.5.3 version directly, the clustering never happens and I get the error.
To give you a bit more overview of the implementation:
The pods use a persistent volume claim on a gluster volume. Each pod is
assigned its own volume on the gluster file system. I run zookeeper as a
stateful set with 3 pods.
Has there been any change on the clustering side of things that makes the new
version not work?
Sample logs:
2018-02-22 19:21:18,078 [myid:1] - ERROR [main:QuorumPeerMain@98] - Unexpected
exception, exiting abnormally
java.lang.RuntimeException: My id 1 not in the peer list
at org.apache.zookeeper.server.quorum.QuorumPeer.start(QuorumPeer.java:770)
at
org.apache.zookeeper.server.quorum.QuorumPeerMain.runFromConfig(QuorumPeerMain.java:185)
at
org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:120)
at
org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:79)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
