gpt4 book ai didi

hadoop - Mesos 0.21.0上的Hadoop 2.5.2-无法获取容器的URI

转载 作者:行者123 更新时间:2023-12-02 18:47:51 24 4
gpt4 key购买 nike

我正在尝试在具有Hadoop 2.5.2的Mesos上运行一个简单的WordCount示例。我已经成功设置了HDFS(实际上是在它后面设置了YARN,并且工作正常)。 Mesos主服务器正在运行,并连接了4个从属服务器。 Mesos的Hadoop库为0.0.8。

Hadoop 2.5.2的配置为(mapred-site.xml):

<configuration>
<property>
<name>mapred.job.tracker</name>
<value>*.*.*.*:9001</value>
</property>
<property>
<name>mapred.job.tracker.http.address</name>
<value>*.*.*.*:50030</value>
</property>
<property>
<name>mapred.jobtracker.taskScheduler</name>
<value>org.apache.hadoop.mapred.MesosScheduler</value>
</property>
<property>
<name>mapred.mesos.taskScheduler</name>
<value>org.apache.hadoop.mapred.JobQueueTaskScheduler</value>
</property>
<property>
<name>mapred.mesos.master</name>
<value>*.*.*.*:5050</value>
</property>
<property>
<name>mapred.mesos.executor.uri</name>
<value>hdfs://*.*.*.*:9000/hadoop-2.5.0-cdh5.2.0.tgz</value>
</property>
</configuration>

我从所有奴隶那里得到了以下日志(示例):

dbpc42: I1202 00:03:12.066195 11232 launcher.cpp:137] Forked child with pid '18714' for container 'c10c2d2b-bf4b-469b-97a2-60c9720773b4'

dbpc42: I1202 00:03:12.068272 11232 containerizer.cpp:571] Fetching URIs for container 'c10c2d2b-bf4b-469b-97a2-60c9720773b4' using command '/opt/mesos-0.21.0/build/src/mesos-fetcher'

dbpc42: I1202 00:03:12.140894 11226 containerizer.cpp:946] Destroying container 'c10c2d2b-bf4b-469b-97a2-60c9720773b4'

dbpc42: E1202 00:03:12.141315 11229 slave.cpp:2787] Container 'c10c2d2b-bf4b-469b-97a2-60c9720773b4' for executor 'executor_Task_Tracker_93' of framework '20141201-225046-698725789-5050-19765-0003' failed to start: Failed to fetch URIs for container 'c10c2d2b-bf4b-469b-97a2-60c9720773b4': exit status 256

dbpc42: I1202 00:03:12.242033 11231 containerizer.cpp:1117] Executor for container 'c10c2d2b-bf4b-469b-97a2-60c9720773b4' has exited dbpc42: I1202 00:03:12.243896 11225 slave.cpp:2898] Executor 'executor_Task_Tracker_93' of framework 20141201-225046-698725789-5050-19765-0003 exited with status 1



作业跟踪器运行良好,使用 hadoop jar命令,卡在 map 0%处的作业减少了0%。在mesos群集信息中, TASKS_LOST计数器一直向上运行,直到我终止该工作为止。 Mesos和JobTracker以root身份运行,作业以 hdfs用户身份运行。

这个URI问题到底是什么?

感谢您的帮助或提示!

(如果需要,我将提供更多信息。)

更新

在运行主计算机的同一台PC上启动从计算机将使任务进入暂存状态。 5,每次。
mapred-mesos.executor.uri已从IP更改为 dbpc41(主PC)。
<property>
<name>mapred.mesos.executor.uri</name>
<value>hdfs://dbpc41:9000/hadoop-2.5.0-cdh5.2.0.tgz</value>
</property

由于(可能)无法获取执行者URI,其他4个从属仍在丢失任务。

这些是与主服务器在同一台PC上运行的第5个从服务器的日志:

I1202 16:17:57.434345 1405 containerizer.cpp:571] Fetching URIs for container '5f33123b-00eb-4e05-9dcc-30f16f5eee44' using command '/opt/mesos-0.21.0/build/src/mesos-fetcher' I1202 16:18:08.620708 1412 slave.cpp:2840] Monitoring executor 'executor_Task_Tracker_445' of framework '20141201-225046-698725789-5050-19765-0012' in container '5f33123b-00eb-4e05-9dcc-30f16f5eee44' I1202 16:18:09.022902 1407 containerizer.cpp:1117] Executor for container '5f33123b-00eb-4e05-9dcc-30f16f5eee44' has exited I1202 16:18:09.022964 1407 containerizer.cpp:946] Destroying container '5f33123b-00eb-4e05-9dcc-30f16f5eee44' W1202 16:18:11.369912 1407 containerizer.cpp:888] Skipping resource statistic for container 5f33123b-00eb-4e05-9dcc-30f16f5eee44 because: Failed to get usage: No process found at 11093 W1202 16:18:11.369971 1407 containerizer.cpp:888] Skipping resource statistic for container 5f33123b-00eb-4e05-9dcc-30f16f5eee44 because: Failed to get usage: No process found at 11093 I1202 16:18:11.399648 1412 slave.cpp:2898] Executor 'executor_Task_Tracker_445' of framework 20141201-225046-698725789-5050-19765-0012 exited with status 1 I1202 16:18:11.401949 1412 slave.cpp:2215] Handling status update TASK_LOST (UUID: 959709c2-5546-41fd-9af3-09f024bb6354) for task Task_Tracker_445 of framework 20141201-225046-698725789-5050-19765-0012 from @0.0.0.0:0 W1202 16:18:11.402245 1409 containerizer.cpp:852] Ignoring update for unknown container: 5f33123b-00eb-4e05-9dcc-30f16f5eee44 I1202 16:18:11.403017 1410 status_update_manager.cpp:317] Received status update TASK_LOST (UUID: 959709c2-5546-41fd-9af3-09f024bb6354) for task Task_Tracker_445 of framework 20141201-225046-698725789-5050-19765-0012 I1202 16:18:11.403437 1406 slave.cpp:2458] Forwarding the update TASK_LOST (UUID: 959709c2-5546-41fd-9af3-09f024bb6354) for task Task_Tracker_445 of framework 20141201-225046-698725789-5050-19765-0012 to master@157.181.165.41:5050 I1202 16:18:11.448752 1409 status_update_manager.cpp:389] Received status update acknowledgement (UUID: 959709c2-5546-41fd-9af3-09f024bb6354) for task Task_Tracker_445 of framework 20141201-225046-698725789-5050-19765-0012 I1202 16:18:11.449354 1408 slave.cpp:3007] Cleaning up executor 'executor_Task_Tracker_445' of framework 20141201-225046-698725789-5050-19765-0012 I1202 16:18:11.449707 1405 gc.cpp:56] Scheduling '/tmp/mesos/slaves/20141201-225046-698725789-5050-19765-S4/frameworks/20141201-225046-698725789-5050-19765-0012/executors/executor_Task_Tracker_445/runs/5f33123b-00eb-4e05-9dcc-30f16f5eee44' for gc 6.99999479755852days in the future I1202 16:18:11.450034 1409 gc.cpp:56] Scheduling '/tmp/mesos/slaves/20141201-225046-698725789-5050-19765-S4/frameworks/20141201-225046-698725789-5050-19765-0012/executors/executor_Task_Tracker_445' for gc 6.9999947929037days in the future I1202 16:18:11.450147 1408 slave.cpp:3084] Cleaning up framework 20141201-225046-698725789-5050-19765-0012 I1202 16:18:11.450213 1406 status_update_manager.cpp:279] Closing status update streams for framework 20141201-225046-698725789-5050-19765-0012 I1202 16:18:11.450381 1412 gc.cpp:56] Scheduling '/tmp/mesos/slaves/20141201-225046-698725789-5050-19765-S4/frameworks/20141201-225046-698725789-5050-19765-0012' for gc 6.99999478812444days in the future I1202 16:18:12.441505 1405 slave.cpp:1083] Got assigned task Task_Tracker_472 for framework 20141201-225046-698725789-5050-19765-0012 I1202 16:18:12.442337 1405 gc.cpp:84] Unscheduling '/tmp/mesos/slaves/20141201-225046-698725789-5050-19765-S4/frameworks/20141201-225046-698725789-5050-19765-0012' from gc I1202 16:18:12.442617 1405 slave.cpp:1193] Launching task Task_Tracker_472 for framework 20141201-225046-698725789-5050-19765-0012 I1202 16:18:12.444263 1405 slave.cpp:3997] Launching executor executor_Task_Tracker_472 of framework 20141201-225046-698725789-5050-19765-0012 in work directory '/tmp/mesos/slaves/20141201-225046-698725789-5050-19765-S4/frameworks/20141201-225046-698725789-5050-19765-0012/executors/executor_Task_Tracker_472/runs/2310c642-02bf-401b-954c-876c88675c31' I1202 16:18:12.444756 1405 slave.cpp:1316] Queuing task 'Task_Tracker_472' for executor executor_Task_Tracker_472 of framework '20141201-225046-698725789-5050-19765-0012 I1202 16:18:12.444793 1406 containerizer.cpp:424] Starting container '2310c642-02bf-401b-954c-876c88675c31' for executor 'executor_Task_Tracker_472' of framework '20141201-225046-698725789-5050-19765-0012' I1202 16:18:12.447434 1406 launcher.cpp:137] Forked child with pid '11549' for container '2310c642-02bf-401b-954c-876c88675c31' I1202 16:18:12.448652 1406 containerizer.cpp:571] Fetching URIs for container '2310c642-02bf-401b-954c-876c88675c31' using command '/opt/mesos-0.21.0/build/src/mesos-fetcher'

最佳答案

检查执行程序日志(stderr中的/tmp/mesos/slaves/...),发现未设置JAVA_HOME,因此hadoop dfs命令无法运行以获取执行程序。 URI非常完美,没有设置JAVA_HOME。另外,启动奴隶时我必须设置HADOOP_HOME

关于hadoop - Mesos 0.21.0上的Hadoop 2.5.2-无法获取容器的URI,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/27237480/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com