You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hadoop map reduce job is running properly.A Spark job make use of Mesos Docker containerizer. when oozie used a map reduce job to schedule that Spark job. Mesos Docker containerizer cannot run.
I’m not sure this Question, any idea on how to resolve this problem?
[Executor registered on agent ] information not be found.It seems like Registered failed, so mesos Docker containerizer cannot run.
mesos system mesos-slave.ERROR
E0213 15:13:48.616093 9896 slave.cpp:2621] Status update acknowledgement (UUID: 5953d089-e259-4f63-9eb6-ca97f73f10f7) for task Task_Tracker_0 of unknown executor
The text was updated successfully, but these errors were encountered:
hadoop no mesos + spark on mesos + oozie
Hadoop map reduce job is running properly.A Spark job make use of Mesos Docker containerizer. when oozie used a map reduce job to schedule that Spark job. Mesos Docker containerizer cannot run.
I’m not sure this Question, any idea on how to resolve this problem?
Build mesos.version ‘0.23.1’.
Hadoop cluster mesos.version ‘1.0.1’.
mesos task running stderr:
I0213 15:13:47.948076 13351 fetcher.cpp:547] Fetched '/etc/docker.tar.gz' to '/var/lib/mesos/slaves/8a2d57b7-3a9b-478d-8fc3-19e3e573ab6c-S18/frameworks/8a2d57b7-3a9b-478d-8fc3-19e3e573ab6c-1166/executors/driver-20170213151343-124182/runs/a8eb3fa4-1919-4b26-a05f-ad3fdcc32aed/docker.tar.gz'
I0213 15:13:48.161221 13629 exec.cpp:161] Version: 1.0.1
I0213 15:13:48.165864 13634 exec.cpp:413] Executor asked to shutdown
[Executor registered on agent ] information not be found.It seems like Registered failed, so mesos Docker containerizer cannot run.
mesos system mesos-slave.ERROR
E0213 15:13:48.616093 9896 slave.cpp:2621] Status update acknowledgement (UUID: 5953d089-e259-4f63-9eb6-ca97f73f10f7) for task Task_Tracker_0 of unknown executor
The text was updated successfully, but these errors were encountered: