Hadoop:Reducer 正在生成错误
我在减少阶段不断收到Exceeded MAX_FAILED_UNIQUE_FETCHES
。
尽管我尝试了网上能找到的所有解决方案。
节点:已安装的服务
Master_Node:Namenode、JobTracker
配置文件附在下面:
core-site.xml
<configuration>
<property>
<name>hadoop.tmp.dir</name>
<value>/usr/local/hadoop-datastore/hadoop-${user.name}</value>
<description>Hadoop Data Store</description>
</property>
<property>
<name>fs.default.name</name>
<value>hdfs://172.16.8.3:54310/</value>
</property>
</configuration>
mapred-site.xml
<configuration>
<property>
<name>mapred.job.tracker</name>
<value>172.16.8.3:54311</value>
</property>
</configuration>
I keep on getting Exceeded MAX_FAILED_UNIQUE_FETCHES
on the reduce phase.
Even though I tried all the solutions I could find online.
Node: Services Installed
Master_Node: Namenode, JobTracker
Configuration files are attached below:
core-site.xml
<configuration>
<property>
<name>hadoop.tmp.dir</name>
<value>/usr/local/hadoop-datastore/hadoop-${user.name}</value>
<description>Hadoop Data Store</description>
</property>
<property>
<name>fs.default.name</name>
<value>hdfs://172.16.8.3:54310/</value>
</property>
</configuration>
mapred-site.xml
<configuration>
<property>
<name>mapred.job.tracker</name>
<value>172.16.8.3:54311</value>
</property>
</configuration>
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
此链接< /a> 似乎表明这可能是网络配置问题。
减速器无法获取地图(由于尝试失败太多),这可能是由于网络/配置问题导致它们无法查询 Jetty 服务器。
免责声明:我没有专业使用过Hadoop
This link seems to indicate that it could be a network configuration problem.
The reducers are failing to fetch the maps (due to failing too many attempts) which could be due to a networking/configuration problem preventing them being able to query the Jetty server.
Disclaimer: I have not used Hadoop professionally
我也遇到了这个错误:Caused by: java.io.IOException: Exceeded MAX_FAILED_UNIQUE_FETCHES;救助。
对我来说,解决方法是在 core-site.xml 和 mapred-site.xml 上使用主机名而不是 IP 地址。
您将需要编辑主机文件并包含主服务器和从服务器
I encountered this error also:Caused by: java.io.IOException: Exceeded MAX_FAILED_UNIQUE_FETCHES; bailing-out.
The fix for me is to use hostnames instead of ip addresses on core-site.xml and mapred-site.xml.
You will need to edit the hosts file and include the masters and the slaves