HBASE 安装后 hbase shell 启动失败问题
来源:互联网 发布:光伏电站数据采集器 编辑:程序博客网 时间:2024/06/13 14:57
1, 安装HBASE, 并且启动成功
[root@MASTER opt]# jps
21920 SecondaryNameNode
2273 HMaster
21441 NameNode
5490 ResourceManager
1844 QuorumPeerMain
2501 HRegionServer
21653 DataNode
3532 Jps
22236 NodeManager
2,尝试运行hbase
ot@MASTER opt]# hbase shell
Java HotSpot(TM) Server VM warning: You have loaded library /root/cluster/opt/hadoop-2.6.0/lib/native/libhadoop.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
2016-11-10 13:54:37,656 WARN [main] util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/root/cluster/opt/hbase-1.2.4/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/root/cluster/opt/hadoop-2.6.0/share/hadoop/common/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
2016-11-10 13:54:53,158 ERROR [main] zookeeper.RecoverableZooKeeper: ZooKeeper exists failed after 4 attempts
2016-11-10 13:54:53,159 WARN [main] zookeeper.ZKUtil: hconnection-0x1a64eae0x0, quorum=10.12.2.182:2181, 10.12.2.224:2181, baseZNode=/hbase Unable to set watcher on znode (/hbase/hbaseid)
org.apache.zookeeper.KeeperException$OperationTimeoutException: KeeperErrorCode = OperationTimeout
at org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.checkZk(RecoverableZooKeeper.java:144)
at org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.exists(RecoverableZooKeeper.java:220)
at org.apache.hadoop.hbase.zookeeper.ZKUtil.checkExists(ZKUtil.java:419)
at org.apache.hadoop.hbase.zookeeper.ZKClusterId.readClusterIdZNode(ZKClusterId.java:65)
at org.apache.hadoop.hbase.client.ZooKeeperRegistry.getClusterId(ZooKeeperRegistry.java:105)
at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.retrieveClusterId(ConnectionManager.java:905)
at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.<init>(ConnectionManager.java:648)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:238)
at org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:218)
at org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:450)
at org.jruby.javasupport.JavaMethod.invokeStaticDirect(JavaMethod.java:362)
at org.jruby.java.invokers.StaticMethodInvoker.call(StaticMethodInvoker.java:58)
at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:312)
at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:169)
at org.jruby.ast.CallOneArgNode.interpret(CallOneArgNode.java:57)
...
3, 经过调查把 hbase-site.xml 中的属性:
从:
<name>hbase.zookeeper.quorum</name>
<value>MASTER, SLAVE</value>
</property>
改为:
MASTER:
<name>hbase.zookeeper.quorum</name>
<value>MASTER</value>
</property>
<name>hbase.zookeeper.quorum</name>
<value>SLAVE</value>
</property>
4, 重新运行,成功了:
root@MASTER opt]# hbase shell
Java HotSpot(TM) Server VM warning: You have loaded library /root/cluster/opt/hadoop-2.6.0/lib/native/libhadoop.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
2016-11-10 14:20:17,256 WARN [main] util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/root/cluster/opt/hbase-1.2.4/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/root/cluster/opt/hadoop-2.6.0/share/hadoop/common/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
HBase Shell; enter 'help<RETURN>' for list of supported commands.
Type "exit<RETURN>" to leave the HBase Shell
Version 1.2.4, r67592f3d062743907f8c5ae00dbbe1ae4f69e5af, Tue Oct 25 18:10:20 CDT 2016
hbase(main):001:0>
- HBASE 安装后 hbase shell 启动失败问题
- HBase启动失败,启动后自动退出
- hbase启动后进程消失,status失败或者list失败。一般是hbase启动失败所致。
- Hbase启动失败
- Hbase 启动失败htrace
- 启动HBase后遇到的一个问题
- HBASE启动/Shell解析
- Hbase的HMaster启动失败
- Hbase HMaster启动问题
- hbase 单机启动问题
- hbase启动HMaster问题
- HBASE启动脚本/Shell解析
- HBASE启动脚本/Shell解析
- HBASE启动脚本/Shell解析
- HBASE启动脚本/Shell解析
- Hbase shell启动报错
- 启动hbase shell的命令
- Hbase服务启动以及shell命令使用遇到的问题
- wempserver apache启动不了,图标显示为黄色
- ubuntu下Qt安装qwt出现的问题
- 一致性哈希
- 四种获取小数点后两位方法
- 2014 Multi-University Training Contest 1 题解
- HBASE 安装后 hbase shell 启动失败问题
- 获取手机屏幕像素及密度--查看当前调用的布局文件
- android 内置APK
- jQuery LigerUI 使用教程
- android控件属性padding
- Android源码结构
- Java学习笔记-单例模式等
- 阶段巨献 - centos+php-fpm+mariaDB+svn+nodejs,配置linux的php和nodejs网站运行环境。
- 最大概率法分词及性能测试