当前位置:   article > 正文

Hadoop 集群维护过程中遇到的报错信息和解决办法_is not sending heartbeats

is not sending heartbeats

1、Connection failed: [Errno 111] Connection refused to XXX:16030

  1. 在ambari上启动某台主机上的regionserver时,启动不了,同时在主机上的/var/log/hbase/ 目录中有日志产生。
  2. 日志hbase-hbase-regionserver-XXX.log 中新增内容:
  3. 20161130日 星期三 10:06:22 CST Starting regionserver on XXX
  4. core file size (blocks, -c) 0
  5. data seg size (kbytes, -d) unlimited
  6. scheduling priority (-e) 0
  7. file size (blocks, -f) unlimited
  8. pending signals (-i) 1031397
  9. max locked memory (kbytes, -l) 64
  10. max memory size (kbytes, -m) unlimited
  11. open files (-n) 10000
  12. pipe size (512 bytes, -p) 8
  13. POSIX message queues (bytes, -q) 819200
  14. real-time priority (-r) 0
  15. stack size (kbytes, -s) 10240
  16. cpu time (seconds, -t) unlimited
  17. max user processes (-u) 16000
  18. virtual memory (kbytes, -v) unlimited
  19. file locks (-x) unlimited
  20. 另外还会产生一个日志文件hs_err_pid16030.log

解决办法:

在hs_err_pid开头的文件中,有提示的办法,在主机上执行命令ulimit -c unlimited,之后在ambari页面上重新启动regionserver,启动成功,告警消失了。

2、ERROR [pool-9-thread-319] BaseProvider:240 - Caught exception getting JMX metrics :

  1. 集群ambari中的指标加载不出来,查看34/var/log/ambari-server/ambari-server.log有如下错误:
  2. 29 Nov 2016 16:18:18,337 ERROR [pool-9-thread-319] BaseProvider:240 - Caught exception getting JMX metrics :
  3. Connection refused, skipping same exceptions for next 5 minutes
  4. java.net.ConnectException: Connection refused

解决办法:
昨天有问题,当时没有解决,今天集群自己恢复了,可能是时间同步的问题

3、There are 1 stale alerts from 1 host(s)

集群时间有问题了,同步时间后自动恢复正常

解决办法链接:
https://community.hortonworks.com/questions/9762/how-to-get-rid-of-stale-alerts-in-ambari.html?page=1&pageSize=10&sort=votes

4、Connection failed: [Errno 111] Connection refused to XXX:50010

  1. 2017-04-18 14:23:25,008 WARN datanode.DataNode (DataNode.java:checkStorageLocations(2439)) - Invalid dfs.datanode.data.dir /data1/hadoop/hdfs/data :
  2. org.apache.hadoop.util.DiskChecker$DiskErrorException: Directory is not writable: /data1/hadoop/hdfs/data
  3. 。。。
  4. 2017-04-18 14:23:26,751 WARN common.Storage (BlockPoolSliceStorage.java:loadBpStorageDirectories(221)) - Failed to analyze storage directories for block pool BP-1071526479-192.16.10.34-1472798972660
  5. java.io.IOException: BlockPoolSliceStorage.recoverTransitionRead: attempt to load an used block storage: /data2/hadoop/hdfs/data/current/BP-1071526479-192.16.10.34-1472798972660
  6. at

Directory is not writable: /data1/hadoop/hdfs/data 。

/dev/sdb1 ext4 3.6T 137G 3.3T 4% /data1

一块磁盘出问题了

解决方法:修改hdfs-sites配置属性
dfs.datanode.failed.volumes.tolerated值为1;重启动datanode即可。

  1. 1、卸载磁盘
  2. 查看使用/data1的进程,并杀掉
  3. [root@XXX ~]# fuser -m /data1
  4. /data1: 4036m 26457c
  5. [root@XXX ~]# kill -9 26457
  6. [root@XXX ~]# fuser -m /data1
  7. /data1: 4036m
  8. [root@XXX ~]# kill -9 4036
  9. 2、卸载磁盘
  10. umount /dev/sdb1 /data1
  11. 3、格式化磁盘
  12. mkfs.ext4 /dev/sdb1

5、DataNode Health: [Live=18, Stale=0, Dead=1]

  1. DataNode Health Summary
  2. DataNode Health: [Live=18, Stale=0, Dead=1]
  3. DataNode Health: [Live=18, Stale=0, Dead=1]

解决办法:

Dead掉的是主机能ping通,但是ssh的时候秒退,估计是客户端连接数过多,就会这样,要修改配置文件,把连接数改大

6、XXX is not sending heartbeats

解决办法:

  1. 1、查看agent是否在运行,显示没有
  2. sudo ambari-agent status
  3. 2、启动agent
  4. sudo ambari-agent start

7、ambari中hbase报错

  1. 2017-08-03 09:20:59,089 INFO [regionserver/XXX/192.16.10.25:16020]
  2. regionserver.HRegionServer: STOPPED:
  3. Unhandled: org.apache.hadoop.hbase.ClockOutOfSyncException:
  4. Server XXX,16020,1501723257281 has been rejected;
  5. Reported time is too far out of sync with master.
  6. Time difference of 224557ms > max allowed of 30000ms

解决办法:

同步集群时间

8、sqoop导数据报错:Container killed on request. Exit code is 143

  1. 调大如下两个属性值
  2. mapreduce.map.memory.mb
  3. mapreduce.reduce.memory.mb

9、ambari中重启某台主机的组件卡住

  1. Aug 2017 09:02:07,516 ERROR [qtp-ambari-client-986626] MetricsRequestHelper:114 - Error getting timeline metrics : Read timed out
  2. 04 Aug 2017 09:02:07,517 ERROR [qtp-ambari-client-986626] MetricsRequestHelper:121 - Error getting timeline metrics : Read timed out Can not connect to collector, socket error.
  3. 04 Aug 2017 09:11:52,441 ERROR [pool-9-thread-58891] BaseProvider:240 - Caught exception getting JMX metrics : Connection refused, skipping same exceptions for next 5 minutes
  4. java.net.ConnectException: Connection refused
  5. at java.net.PlainSocketImpl.socketConnect(Native Method)
  6. at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)

解决办法:

参考https://community.hortonworks.com/questions/49766/ambari-unable-to-start-any-service-after-successfu.html

  1. 解决方法:
  2. a)在data主机重启ambari-agent
  3. ambari-agent restart
  4. b) 在master1主机重启ambari-server
  5. ambari-server restart

10、Connection failed to http:/XXX:50075 (<urlopen error [Errno 111] Connection refused>)

 

11、通过beeline方式调用hql报错问题

  1. Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
  2. [2017-04-11 10:52:25,713] {bash_operator.py:77} INFO - at java.util.Arrays.copyOf(Arrays.java:3332)
  3. [2017-04-11 10:52:25,713] {bash_operator.py:77} INFO - at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:137)
  4. [2017-04-11 10:52:25,713] {bash_operator.py:77} INFO - at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:121)
  5. [2017-04-11 10:52:25,713] {bash_operator.py:77} INFO - at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:569)
  6. [2017-04-11 10:52:25,714] {bash_operator.py:77} INFO - at java.lang.StringBuffer.append(StringBuffer.java:369)
  7. [2017-04-11 10:52:25,714] {bash_operator.py:77} INFO - at java.io.BufferedReader.readLine(BufferedReader.java:370)
  8. [2017-04-11 10:52:25,714] {bash_operator.py:77} INFO - at java.io.BufferedReader.readLine(BufferedReader.java:389)
  9. [2017-04-11 10:52:25,714] {bash_operator.py:77} INFO - at jline.console.history.FileHistory.load(FileHistory.java:69)
  10. [2017-04-11 10:52:25,714] {bash_operator.py:77} INFO - at jline.console.history.FileHistory.load(FileHistory.java:55)
  11. [2017-04-11 10:52:25,714] {bash_operator.py:77} INFO - at jline.console.history.FileHistory.<init>(FileHistory.java:44)
  12. [2017-04-11 10:52:25,714] {bash_operator.py:77} INFO - at org.apache.hive.beeline.BeeLine.getConsoleReader(BeeLine.java:873)
  13. [2017-04-11 10:52:25,715] {bash_operator.py:77} INFO - at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:780)
  14. [2017-04-11 10:52:25,715] {bash_operator.py:77} INFO - at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:485)
  15. [2017-04-11 10:52:25,715] {bash_operator.py:77} INFO - at org.apache.hive.beeline.BeeLine.main(BeeLine.java:468)
  16. [2017-04-11 10:52:25,715] {bash_operator.py:77} INFO - at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  17. [2017-04-11 10:52:25,715] {bash_operator.py:77} INFO - at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  18. [2017-04-11 10:52:25,715] {bash_operator.py:77} INFO - at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  19. [2017-04-11 10:52:25,715] {bash_operator.py:77} INFO - at java.lang.reflect.Method.invoke(Method.java:497)
  20. [2017-04-11 10:52:25,715] {bash_operator.py:77} INFO - at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
  21. [2017-04-11 10:52:25,715] {bash_operator.py:77} INFO - at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
  22. [2017-04-11 10:52:26,055] {bash_operator.py:80} INFO - Command exited with return code 0

解决办法:
通过查找资料和测试,发现原因是 ~/.beeline/history 文件过大导致的,把该文件删除后测试成功
https://issues.apache.org/jira/browse/HIVE-10836

 

声明:本文内容由网友自发贡献,不代表【wpsshop博客】立场,版权归原作者所有,本站不承担相应法律责任。如您发现有侵权的内容,请联系我们。转载请注明出处:https://www.wpsshop.cn/w/小蓝xlanll/article/detail/148373?site
推荐阅读
相关标签
  

闽ICP备14008679号