3次重试后ZooKeeper存在失败 [英] ZooKeeper exists failed after 3 retries

问题描述

我在伪分布式模式下运行Hadoop-1.2.1和HBase-0.94.11。

由于电源故障，Hadoop和HBase设置下降。下一次，当我重新启动我的机器和伪分布设置时，HBase在HBase shell中停止了以下错误：

  13/11/27 13:53:27错误zookeeper.RecoverableZooKeeper：3次重试后ZooKeeper存在失败
 13/11/27 13:53:27 WARN zookeeper.ZKUtil：hconnection无法在znode上设置监视器（/ HBase的/ hbaseid）
 $ org.apache.zookeeper.KeeperException ConnectionLossException：KeeperErrorCode = ConnectionLoss为/ HBase的/ hbaseid 
。在org.apache.zookeeper.KeeperException.create（KeeperException.java:99）
在org.apache.zookeeper.KeeperException.create（KeeperException.java:51）
在org.apache.zookeeper.ZooKeeper.exists（ZooKeeper.java:1041）
在org.apache.hadoop。 hbase.zookeeper.RecoverableZooKeeper.exists（RecoverableZooKeeper.java:172）
在org.apache.had oop.hbase.zookeeper.ZKUtil.checkExists（ZKUtil.java:450）
处org.apache org.apache.hadoop.hbase.zookeeper.ClusterId.readClusterIdZNode（ClusterId.java:61）
。 hadoop.hbase.zookeeper.ClusterId.getId（ClusterId.java:50）
在org.apache.hadoop.hbase.zookeeper.ClusterId.hasId（ClusterId.java:44）
在org.apache。 hadoop.hbase.client.HConnectionManager $ HConnectionImplementation.ensureZookeeperTrackers（HConnectionManager.java:720）
在org.apache.hadoop.hbase.client.HConnectionManager $ HConnectionImplementation.getMaster（HConnectionManager.java:789）
。在org.apache.hadoop.hbase.client.HBaseAdmin<初始化>（HBaseAdmin.java:129）
。在sun.reflect.NativeConstructorAccessorImpl.newInstance0（本机方法）
。在sun.reflect.NativeConstructorAccessorImpl。 newInstance（NativeConstructorAccessorImpl.java:57）
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance（DelegatingConstructorAccessorImpl.java:45）
 at java.lang.reflect.Co nstructor.newInstance（Constructor.java:526）
  

以下是过程：

  hduser @ user-ubuntu：〜$ jps 
 16914 NameNode 
 19955 Jps 
 29460 Main 
 17728 TaskTracker 
 19776 HMaster 
 17490 JobTracker 
 17392 SecondaryNameNode 
  

解决方案

您确定您的Zookeeper进程正在运行（您的jps列表不显示QuorumPeerMain的条目）？ jps堆栈可能不会显示所有正在运行的java进程 - 尝试使用 ps axww | grep QuorumPeerMain 。

如果您的zookeeper拒绝启动，请检查其日志以查看是否存在某些堆栈跟踪线索。 $ b

I am running Hadoop-1.2.1 and HBase-0.94.11 in a pseudo-distributed mode.

Due to power failure Hadoop and HBase set up went down.Next time when I restarted my machine and the pseudo-distribution set up, HBase stopped working with the following errors on HBase shell:

13/11/27 13:53:27 ERROR zookeeper.RecoverableZooKeeper: ZooKeeper exists failed after 3 retries
13/11/27 13:53:27 WARN zookeeper.ZKUtil: hconnection Unable to set watcher on znode (/hbase/hbaseid)
org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /hbase/hbaseid
    at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
    at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
    at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1041)
    at org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.exists(RecoverableZooKeeper.java:172)
    at org.apache.hadoop.hbase.zookeeper.ZKUtil.checkExists(ZKUtil.java:450)
    at org.apache.hadoop.hbase.zookeeper.ClusterId.readClusterIdZNode(ClusterId.java:61)
    at org.apache.hadoop.hbase.zookeeper.ClusterId.getId(ClusterId.java:50)
    at org.apache.hadoop.hbase.zookeeper.ClusterId.hasId(ClusterId.java:44)
    at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.ensureZookeeperTrackers(HConnectionManager.java:720)
    at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getMaster(HConnectionManager.java:789)
    at org.apache.hadoop.hbase.client.HBaseAdmin.<init>(HBaseAdmin.java:129)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:526)

Following are the processes :

hduser@user-ubuntu:~$ jps
16914 NameNode
19955 Jps
29460 Main
17728 TaskTracker
19776 HMaster
17490 JobTracker
17392 SecondaryNameNode

解决方案

Are you sure your Zookeeper process is running (your jps listing doesn't show an entry for QuorumPeerMain)? The jps stack may not show all java processes running - try using a ps axww | grep QuorumPeerMain.

If your zookeeper refuses to start, check its logs to see if there are some stack trace clues

这篇关于3次重试后ZooKeeper存在失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！