zookeeper常遇错误详解

最新推荐文章于 2024-11-04 20:02:57 发布

转载最新推荐文章于 2024-11-04 20:02:57 发布 · 2.5k 阅读

0 ·

CC 4.0 BY-SA版权

原文链接：http://www.cnblogs.com/jieran/p/9196154.html

文章标签：

#大数据 #java

本文介绍了当尝试启动ZooKeeper遇到错误时的排查步骤，包括检查QuorumPeerMain进程状态、确认2181端口未被占用、确保myid文件顺序正确及按照myid顺序启动等操作。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

错误展示：

./zkServer.sh status
JMX enabled by default
Using config: /home/hadoop/zookeeper-3.4.5-cdh5.5.2/bin/../conf/zoo.cfg
Error contacting service. It is probably not running.

./zkServer.sh restart
JMX enabled by default
Using config: /home/hadoop/zookeeper-3.4.5-cdh5.5.2/bin/../conf/zoo.cfg
JMX enabled by default
Using config: /home/hadoop/zookeeper-3.4.5-cdh5.5.2/bin/../conf/zoo.cfg
Stopping zookeeper ... no zookeeper to stop (could not find file /tmp/zookeeper
/home/hadoop/zookeeper-3.4.5-cdh5.5.2/data/zookeeper_server.pid)
JMX enabled by default
Using config: /home/hadoop/zookeeper-3.4.5-cdh5.5.2/bin/../conf/zoo.cfg
Starting zookeeper ... ./zkServer.sh: line 120: [: /tmp/zookeeper: binary operator expected
STARTED

cat zookeeper.out

2018-06-18 20:48:43,134 [myid:1] - ERROR [main:QuorumPeerMain@94] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use

说明2181端口被占用。

答题解决方案套路：

1，查看是否有QuorumPeerMain进程，

2通过netstat -nltp | grep 2181检查是否已被占用，如果被占用，kill pid

3/data/myid 必须是有顺序的，比如有三台机器，必须按1,2,3.

4启动顺序必须安myid的顺序启动

这样解决之后zookeeper就能正常启动了。

jps

QuorumPeerMain

./zkServer.sh status

Mode: follower

Mode: leader