【Hadoop】Hbase分布式链接出错的问题,启动后不能连上其他节点处理问题。一直报错The node /hbase is not in ZooKeeper.不能同步的问题。
2016-12-09 20:22
537 查看
以下是执行报错信息
以下是日志信息:
很明显说明2181端口被占用了,又由于查了半天不知道这个端口是被哪个占用的,
我个人猜想是不是hadoop中间件系列哪个里面开了这个自带的zookeeper把这个默认的端口给占用了。
又不能确定,所以也不好kill掉这个端口,因此只能修改默认端口:
hbase-site.xml中修改
让2181变成2182
执行后结果
信息显示
log显示
可以看到成功。
同时我们打开web shell,看看之前输入list时候 提示的链接不上端口2181是否还存在。
顺利执行
另外,在整个过程中,对配置的疑惑也顺便写下来。
第一,
即使是一个master 三个slave
但配置中quorum只能写其他三个slave
第二,为了保险起见,还是自己配置zookeeper吧……自带的都是坑(泪
那么你还需要修改环境hbase-env.sh。
第三,如果有报错说查看是否zookeeper.znode.parent配置好,
你直接在xml中定义会更好,免得出其他差错。
同时要配合rootserver一起来。
第四,你要不是伪分布式,请一定要指定
2016-12-09 19:38:17,672 ERROR [main] client.ConnectionManager$HConnectionImplementation: The node /hbase is not in ZooKeeper. It should have been written by the master. Check the value configured in 'zookeeper.znode.parent'. There could be a mismatch with the one configured in the master. 2016-12-09 19:38:17,779 ERROR [main] client.ConnectionManager$HConnectionImplementation: The node /hbase is not in ZooKeeper. It should have been written by the master. Check the value configured in 'zookeeper.znode.parent'. There could be a mismatch with the one configured in the master. 2016-12-09 19:38:17,981 ERROR [main] client.ConnectionManager$HConnectionImplementation: The node /hbase is not in ZooKeeper. It should have been written by the master. Check the value configured in 'zookeeper.znode.parent'. There could be a mismatch with the one configured in the master. 2016-12-09 19:38:18,284 ERROR [main] client.ConnectionManager$HConnectionImplementation: The node /hbase is not in ZooKeeper. It should have been written by the master. Check the value configured in 'zookeeper.znode.parent'. There could be a mismatch with the one configured in the master. 2016-12-09 19:38:18,786 ERROR [main] client.ConnectionManager$HConnectionImplementation: The node /hbase is not in ZooKeeper. It should have been written by the master. Check the value configured in 'zookeeper.znode.parent'. There could be a mismatch with the one configured in the master. 2016-12-09 19:38:19,790 ERROR [main] client.ConnectionManager$HConnectionImplementation: The node /hbase is not in ZooKeeper. It should have been written by the master. Check the value configured in 'zookeeper.znode.parent'. There could be a mismatch with the one configured in the master. 2016-12-09 19:38:21,797 ERROR [main] client.ConnectionManager$HConnectionImplementation: The node /hbase is not in ZooKeeper. It should have been written by the master. Check the value configured in 'zookeeper.znode.parent'. There could be a mismatch with the one configured in the master. ERROR: The node /hbase is not in ZooKeeper. It should have been written by the master. Check the value configured in 'zookeeper.znode.parent'. There could be a mismatch with the one configured in the master.
以下是日志信息:
2016-12-09 19:54:33,045 ERROR [main] master.HMasterCommandLine: Master exiting java.io.IOException: Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum. at org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:212) at org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:137) at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) at org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126) at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2436) 2016-12-09 19:54:33,058 INFO [Thread-2] server.NIOServerCnxn: Closed socket connection for client /127.0.0.1:3168 (no session established for client)
很明显说明2181端口被占用了,又由于查了半天不知道这个端口是被哪个占用的,
我个人猜想是不是hadoop中间件系列哪个里面开了这个自带的zookeeper把这个默认的端口给占用了。
又不能确定,所以也不好kill掉这个端口,因此只能修改默认端口:
hbase-site.xml中修改
让2181变成2182
<property> <name>hbase.zookeeper.property.clientPort</name> <value>2182</value> </property>
执行后结果
信息显示
[root@master bin]# ./start-hbase.sh starting master, logging to /home/hbase/logs/hbase-root-master-master.out Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
log显示
[root@master bin]# ./start-hbase.sh starting master, logging to /home/hbase/logs/hbase-root-master-master.out Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
可以看到成功。
同时我们打开web shell,看看之前输入list时候 提示的链接不上端口2181是否还存在。
hbase(main):001:0> list TABLE 0 row(s) in 0.7930 seconds => [] hbase(main):002:0>
顺利执行
另外,在整个过程中,对配置的疑惑也顺便写下来。
第一,
即使是一个master 三个slave
但配置中quorum只能写其他三个slave
<property> <name>base.zookeeper.quorum</name> <value>slave1,slave2,slave3</value> </property>
第二,为了保险起见,还是自己配置zookeeper吧……自带的都是坑(泪
那么你还需要修改环境hbase-env.sh。
export HBASE_MANAGES_ZK=false
第三,如果有报错说查看是否zookeeper.znode.parent配置好,
你直接在xml中定义会更好,免得出其他差错。
同时要配合rootserver一起来。
<property> <name>zookeeper.znode.parent</name> <value>/hbase</value> <description>Root ZNode for HBase in ZooKeeper. All of HBase's ZooKeeper files that are configured with a relative path will go under this node. By default, all of HBase's ZooKeeper file path are configured with a relative path, so they will all go under this directory unless changed. </description> </property> <property> <name>zookeeper.znode.rootserver</name> <value>root-region-server</value> <description>Path to ZNode holding root region location. This is written by the master and read by clients and region servers. If a relative path is given, the parent folder will be ${zookeeper.znode.parent}. By default, this means the root location is stored at /hbase/root-region-server. </description> </property>
第四,你要不是伪分布式,请一定要指定
<property> <name>hbase.cluser.distributed</name> <value>true</value> </property>
相关文章推荐
- datenode节点超时时间设置,Hadoop启动不正常,HDFS冗余数据块的自动删除,NameNode安全模式问题,ntp时间服务同步,机架感知配置
- 从其他机子上复制过来的一些代码编译时出错的问题处理
- windows xp 一直停留在启动窗口不能进入桌面的问题
- hadoop运行故障问题解决1——datanode节点启动后自动关闭
- hadoop 启动后yarn不能监控问题记录
- Elasticsearch部分节点不能发现集群(脑裂)问题处理
- 关于virtualbox不能为虚拟电脑启动一个新任务报错 GetLastError=1790(其他错误id也可以一试)的问题
- 最近遇到一个问题SQLSERVER2005 目录名称无效(批处理过程出错,不能查询)
- Mysql PXC 问题从节点不能启动问题
- 在虚拟机环境下,电脑间拷贝配置好的伪分布式Hadoop环境,出现namenode不能启动的问题!
- ElasticSearch集群未连接 无法发现节点(windows环境)以及windows环境下设置服务 不能自动启动的问题
- Hadoop启动后Jobtracker一直是initializing状态的问题解决
- hadoop中slaves的datanode不能正常启动问题
- genymotion5.1启动一直卡在启动界面或者是一直卡在启动优化界面问题处理
- VMware ESX4的HA配置问题----有节点不能启动HA
- 惭入佳境之HADOOP的NAMENODE不能正常启动的问题解决
- Hadoop中Datanode节点启动后自动停止问题
- hadoop 安装出现的几种异常的处理方法,hadoop无法启动,no namenode to stop问题的解决方法,no datanode
- Hadoop错误1_Hadoop分布式及伪分布式下DataNode不能启动的问题
- eclipse 启动后,啥也不干,就一直在loading descriptor for XXX (XXX为工程名),,其他什么操作都不能操作。 如下图所示,保存文件也无法保存。 这个怎么办?一年好几天,什么都干不了!!!!!