详解hbase搭建遇到问题及解决方法
java.net.NoRouteToHostException: No route to host at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:368) at org.apache.zookeeper.server.quorum.QuorumCnxManager.connectAll(QuorumCnxManager.java:402) at org.apache.zookeeper.server.quorum.FastLeaderElection.lookForLeader(FastLeaderElection.java:840) at org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:762) 2015-05-19 10:26:26,983 [myid:1] - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@849] - Notification time out: 800解决方法
此问题产生的主要原因是因为zookeeper集群未关闭防火墙。
执行下面命令后仍然报上面的错误:
systemctl start iptables.service
经过仔细查找后发现,CentOS 7.0默认使用的是firewall作为防火墙,需要执行如下命令关闭防火墙:
systemctl stop firewalld.service #停止firewall
systemctl disable firewalld.service #禁止firewall开机启动
关闭各个节点防火墙后,重启zookeeper进程,就可以解决上述问题了。
Caused by: java.io.IOException: Couldnt set up IO streams at org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:786) at org.apache.hadoop.ipc.Client$Connection.access$2800(Client.java:368) at org.apache.hadoop.ipc.Client.getConnection(Client.java:1521) at org.apache.hadoop.ipc.Client.call(Client.java:1438) ... 60 more Caused by: java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:713) at org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:779)解决方法
/etc/security/limits.conf
/etc/security/limits.d/90-nproc.conf
* hard nproc 65536 * soft nproc 65536 * hard nofile 65536 * soft nofile 655363.增加thrift server的线程数
2015-06-05 12:46:37,756 INFO [thrift-worker-6] client.AsyncProcess: #79, waiting for 72000 actions to finish 2015-06-05 12:46:37,756 INFO [thrift-worker-9] client.AsyncProcess: #79, waiting for 48908 actions to finish 2015-06-05 12:46:37,855 INFO [thrift-worker-8] client.AsyncProcess: #79, waiting for 72000 actions to finish 2015-06-05 12:46:38,198 INFO [thrift-worker-2] client.AsyncProcess: #1, waiting for 78000 actions to finish 2015-06-05 12:46:38,762 INFO [thrift-worker-13] client.AsyncProcess: #79, waiting for 72000 actions to finish 2015-06-05 12:46:39,547 INFO [thrift-worker-0] client.AsyncProcess: #17, waiting for 78000 actions to finish 2015-06-05 12:47:55,612 INFO [thrift-worker-9] client.AsyncProcess: #79, waiting for 108000 actions to finish 2015-06-05 12:47:55,912 INFO [thrift-worker-6] client.AsyncProcess: #79, waiting for 114000 actions to finish解决方法
增加thriftServer线程数
hbase-daemon.sh start thrift threadpool -m 200 -w 500
在hbase_home目录下的logs目录中可以看到启动日志信息如下:
INFO [main] thrift.ThriftServerRunner: starting TBoundedThreadPoolServer on /0.0.0.0:9090; min worker threads=200, max worker threads=500, max queued requests=1000
hbase-daemon.sh start thrift –threadpool -m4. zookeeper使用内存大的问题
Heap Configuration配置中我们可以看到,配置的heap内存很大,现在我们修改zkServer.sh脚本减小MaxHeapSize,具体步骤如下:
* 打开zookeeper安装目录下bin文件夹中的zkServer.sh
* 在 zkServer.sh文件的49行处加入 JVMPARAM= -Xms1000M -Xmx1000M -Xmn512M
* 然后修改zkServer.sh 109~110行出的内容。
修改前如下:
nohup "$JAVA" "-Dzookeeper.log.dir=${ZOO_LOG_DIR}" "-Dzookeeper.root.logger=${ZOO_LOG4J_PROP}" / -cp "$CLASSPATH" $JVMFLAGS $ZOOMAIN "$ZOOCFG" "$_ZOO_DAEMON_OUT" 2 1 /dev/null
修改后如下(将在49上添加的JVMPARAM参数项添加在JVMFLAGS后面):
nohup "$JAVA" "-Dzookeeper.log.dir=${ZOO_LOG_DIR}" "-Dzookeeper.root.logger=${ZOO_LOG4J_PROP}" / -cp "$CLASSPATH" $JVMFLAGS $JVMPARAM $ZOOMAIN "$ZOOCFG" "$_ZOO_DAEMON_OUT" 2 1 /dev/null
打开 zookeeper/bin/zkEnv.sh 文件,在zkEvn.sh中49~52行处有如下内容:
if [ -f "$ZOOCFGDIR/java.env" ] . "$ZOOCFGDIR/java.env" fi
该文件已经明确说明有独立JVM内存的设置文件,路径是zookeeper/conf/java.env
安装的时候这个路径下没有有java.env文件,需要自己新建一个:
* vim java.env
* java.env文件内容如下:
#!/bin/sh # heap size MUST be modified according to cluster environment export JVMFLAGS="-Xms512m -Xmx1024m $JVMFLAGS"
[hadoop@hadoop202 conf]$ jmap -heap 10151 Attaching to process ID 10151, please wait... Debugger attached successfully. Server compiler detected. JVM version is 24.71-b01 using thread-local object allocation. Parallel GC with 18 thread(s) Heap Configuration: MinHeapFreeRatio = 0 MaxHeapFreeRatio = 100 MaxHeapSize = 1073741824 (1024.0MB) NewSize = 1310720 (1.25MB) MaxNewSize = 17592186044415 MB OldSize = 5439488 (5.1875MB) NewRatio = 2 SurvivorRatio = 8 PermSize = 21757952 (20.75MB) MaxPermSize = 85983232 (82.0MB) G1HeapRegionSize = 0 (0.0MB) Heap Usage: PS Young Generation Eden Space: capacity = 135266304 (129.0MB) used = 43287608 (41.28227996826172MB) free = 91978696 (87.71772003173828MB) 32.00176741725715% used From Space: capacity = 22020096 (21.0MB) used = 0 (0.0MB) free = 22020096 (21.0MB) 0.0% used To Space: capacity = 22020096 (21.0MB) used = 0 (0.0MB) free = 22020096 (21.0MB) 0.0% used PS Old Generation capacity = 358088704 (341.5MB) used = 0 (0.0MB) free = 358088704 (341.5MB) 0.0% used PS Perm Generation capacity = 22020096 (21.0MB) used = 8887040 (8.475341796875MB) free = 13133056 (12.524658203125MB) 40.358770461309526% used 2699 interned Strings occupying 217008 bytes.
原创文章,作者:ItWorker,如若转载,请注明出处:https://blog.ytso.com/57792.html
apachecentosiptablesjava相关文章
- HBase常见面试题[通俗易懂]
- c# taskscheduler使用场合_hbase shell put
- HBase常见运维工具整理,满足你的维护需要
- Hbase(三) hbase协处理器与二级索引详解大数据
- Hbase(五) hbase内部原理详解大数据
- Hbase(六) hbase Java API详解大数据
- HBase-1.2.1之HRegionServer启动源码学习详解大数据
- HBase笔记详解大数据
- hbase遇到问题及解决方法详解大数据
- HBase流量限制和表负载均衡剖析详解大数据
- hbase-1.2.1之scan、batch操作的源码学习详解编程语言
- Redis与Hbase:探索高效缓存和分布式数据库的最佳实践(redis与hbase)
- 深度挖掘:HBase与Oracle的比较(hbase oracle)
- Hbase与Oracle数据库深入比较(hbase与oracle)
- Redis实现从HBase中批量读取数据(redis读取hbase)