Hbase排错:Hmaster就是无法启动起来
2018-01-12 14:42
204 查看
hbase报错
执行命令:start-hbase.sh
其它节点的HRegionServer够全部启动, 就是 Hmaster启动不来。
日志查看:
Caused by: java.net.UnknownHostException ... 32 more 2018-01-12 14:32:38,385 INFO [geeke3:16000.activeMasterManager] regionserver.HRegionServer: STOPPED: Unhandled exception. Starting shutdown. 2018-01-12 14:32:41,389 INFO [master/geeke3/192.168.1.123:16000] ipc.RpcServer: Stopping server on 16000 2018-01-12 14:32:41,391 INFO [RpcServer.listener,port=16000] ipc.RpcServer: RpcServer.listener,port=16000: stopping 2018-01-12 14:32:41,394 INFO [RpcServer.responder] ipc.RpcServer: RpcServer.responder: stopped 2018-01-12 14:32:41,394 INFO [RpcServer.responder] ipc.RpcServer: RpcServer.responder: stopping 2018-01-12 14:32:41,397 INFO [master/geeke3/192.168.1.123:16000] regionserver.HRegionServer: Stopping infoServer 2018-01-12 14:32:41,408 INFO [master/geeke3/192.168.1.123:16000] mortbay.log: Stopped SelectChannelConnector@0.0.0.0:16010 2018-01-12 14:32:41,410 INFO [master/geeke3/192.168.1.123:16000] regionserver.HRegionServer: stopping server geeke3,16000,1515738750238 2018-01-12 14:32:41,410 INFO [master/geeke3/192.168.1.123:16000] client.ConnectionManager$HConnectionImplementation: Closing zookeeper sessionid=0x260e8e609440005 2018-01-12 14:32:41,414 INFO [master/geeke3/192.168.1.123:16000-EventThread] zookeeper.ClientCnxn: EventThread shut down 2018-01-12 14:32:41,415 INFO [master/geeke3/192.168.1.123:16000] zookeeper.ZooKeeper: Session: 0x260e8e609440005 closed 2018-01-12 14:32:41,418 INFO [master/geeke3/192.168.1.123:16000] regionserver.HRegionServer: stopping server geeke3,16000,1515738750238; all regions closed. 2018-01-12 14:32:41,419 INFO [master/geeke3/192.168.1.123:16000] hbase.ChoreService: Chore service for: geeke3,16000,1515738750238 had [] on shutdown 2018-01-12 14:32:41,435 INFO [master/geeke3/192.168.1.123:16000] ipc.RpcServer: Stopping server on 16000 2018-01-12 14:32:41,461 INFO [master/geeke3/192.168.1.123:16000] zookeeper.ZooKeeper: Session: 0x260e8e609440004 closed 2018-01-12 14:32:41,461 INFO [master/geeke3/192.168.1.123:16000] regionserver.HRegionServer: stopping server geeke3,16000,1515738750238; zookeeper connection closed. 2018-01-12 14:32:41,462 INFO [master/geeke3/192.168.1.123:16000] regionserver.HRegionServer: master/geeke3/192.168.1.123:16000 exiting 2018-01-12 14:32:41,462 INFO [main-EventThread] zookeeper.ClientCnxn: EventThread shut down
问题解决:
冷静下来,认为自己以前替换过Hadoop下jar包。如果回滚到以前,重新来一次呢?
于是做了下面几步:
1. 删掉每个节点下的Hbase;
2. 重新解压开一个新的hbase包;
3. 重新将配置文件写一遍;
4. 分发到每个节点;
5. 再次启动hbase。
这次报错终于不一样的了, 同时也没有什么aws3的相关问题报错。
看看这个报错:
// 关键一句放出来 hbase/tmp/local/jars, DynamicClassLoader failed to init
想象配置文件上就配置过几个属性, 有关“tmp”的就有一个。要不把它注释掉吧。
于是注释掉每个hbas配置文件中的属性:
<property> <name>hbase.tmp.dir</name> <value>/opt/software/hbase/tmp</value> </property>
再次启动,泪奔,Hbase终于正常,执行命令也正常。
相关文章推荐
- hbase中hmaster启动不起来
- HBase的shell命令无法使用,如上图,与Hbase对应的HMaster进程没有启动
- Hbase的HRegionServer进程无法和HMaster同步停止
- apache无法启动的排错方法
- HBase因节点时间不同步无法启动regionserver
- eclise中启动Hbase的Hmaster,玩玩shell
- hbase环境搭建,hmaster启动后会掉解决办法
- php-fpm启动不起来,php-fpm无法启动的一种情况
- HBase1.0.0版源码分析之HMaster启动代码分析(2)
- hbase无法启动Regionserver:Failed construction of Regionserver: class org.apache.hadoop.hbase.regions问题解决
- HBase1.0.0版源码分析之HMaster启动代码分析(1)
- Hbase的HMaster启动失败
- 无法启动Hbase hbase-default.xml file seems to be for and old version of HBase
- HBase因时间不同步无法启动regionserver
- hbase启动HMaster问题
- hadoop namenode重新格式化以后hbase的hmaster进程启动后马上消失
- HBase启动后HMaster挂掉的一种解决方案
- hadoop hbase集群断电数据块被破坏无法启动
- CDH5 下HBase组件无法启动
- hbase源码系列(六)HMaster启动过程