Bad connect ack with firstBadLink as x.x.x.x:50010异常
来源:互联网 发布:山东黄金历史交易数据 编辑:程序博客网 时间:2024/05/24 05:36
问题:
由于Hadoop集群处理作业的需要,为已有的Hadoop集群添加了两个新的节点,但在运行Hadoop作业时,出现了如下问题:
[org.apache.hadoop.hdfs.DFSClient]-[INFO] Exception in createBlockOutputStream x.x.x.x:50010java.io.IOException: Bad connect ack with firstBadLink as x.x.x.x:50010
[org.apache.hadoop.hdfs.DFSClient]-[INFO] Abandoning block blk_-5854021773381781788_14313
[org.apache.hadoop.hdfs.DFSClient]-[INFO] Excluding datanode x.x.x.x:50010
[org.apache.hadoop.hdfs.DFSClient]-[INFO] Exception in createBlockOutputStream x.x.x.x:50010java.io.IOException: Bad connect ack with firstBadLink as x.x.x.x:50010
[org.apache.hadoop.hdfs.DFSClient]-[INFO] Abandoning block blk_-1750664886280243638_14313
[org.apache.hadoop.hdfs.DFSClient]-[INFO] Excluding datanode x.x.x.x:50010
只有新增加的两个节点是有问题,而且都是说关于datanode,端口号50010,访问不了可能就是有阻止访问的设置。
运行的操作系统是:centos6.7
解决方案:
关闭iptables
命令:service iptables stop
虽然这样可以解决,关闭iptables也就意味着所有的端口开放了,更建议通过在iptables中配置端口的方式来解决,也更加安全。
- Bad connect ack with firstBadLink as x.x.x.x:50010异常
- DataNode上执行文件读写时报java.io.IOException: Bad connect ack with firstBadLink as 192.168.X.X错误解决记录
- Hadoop异常:Bad connect ack with firstBadLink
- Bad connect ack with firstBadLink 192.168.*.*:50010
- java.io.IOException: Bad connect ack with firstBadLink as
- hadoop报错java.io.IOException: Bad connect ack with firstBadLink as 192.168.1.218:50010
- Bad connect ack with firstBadLink 192.168.1.14:50010
- datanode Bad connect ack with firstBadLink
- Hadoop异常处理 Bad connect ack with firstBadLink (No route to host )
- 向HDFS上传文件报 java.io.IOException: Bad connect ack with firstBadLink异常
- $X
- X
- X
- X
- x
- x
- X
- /x
- 实现SmartForms 连续打印
- Android进程管理之数据格式化类TextFormat
- LBP局部二值模式研究(待完善)
- HttpClient批量上传文件(二)AsyncTask+HttpClient
- 关于Golang中database/sql包的学习笔记
- Bad connect ack with firstBadLink as x.x.x.x:50010异常
- 系统构建堆的函数
- ALE IDoc & RFC of SAP
- JavaScript函数参数以及变量声明讨论
- 高德地图的使用简单介绍
- 临时表空间管理
- 我的c学习:if控制语句 求一元二次方程的根
- VxWorks中logMsg与printf的区别
- Golang Web编程的Get和Post请求发送与解析