zookeeper集群节点一直LOOKING

https://segmentfault.com/q/1010000007101475

2022-07-11 18:49:40,799 [myid:1] - INFO  [WorkerSender[myid=1]:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (3, 1)
2022-07-11 18:49:40,800 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@595] - Notification: 1 (message format version), 3 (n.leader), 0x1400000029 (n.zxid), 0x1 (n.round), FOLLOWING (n.state), 2 (n.sid), 0x15 (n.peerEpoch) LOOKING (my state)
2022-07-11 18:50:32,000 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@847] - Notification time out: 60000
2022-07-11 18:50:32,001 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@595] - Notification: 1 (message format version), 1 (n.leader), 0x0 (n.zxid), 0x1 (n.round), LOOKING (n.state), 1 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)

后台一直Have smaller server identifier, so dropping the connection: (2, 1)】

解决方法:按照集群配置内的PID 顺序 从小到大依次启动

posted @ 2022-07-11 18:55  zbjice  阅读(597)  评论(0)    收藏  举报