[ 
https://issues.apache.org/jira/browse/MESOS-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone reassigned MESOS-475:
--------------------------------

    Assignee: Benjamin Hindman  (was: Vinod Kone)

Is this going to be fixed by the cluster abstraction you are working on?

If not, feel free to kick it back to me.
                
> make hadoop is broken on trunk
> ------------------------------
>
>                 Key: MESOS-475
>                 URL: https://issues.apache.org/jira/browse/MESOS-475
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 0.13.0
>            Reporter: Vinod Kone
>            Assignee: Benjamin Hindman
>             Fix For: 0.13.0
>
>
> Due to the recent change in process isolator to use mesos launcher, make 
> hadoop fails on finding the mesos-launcher.
> I0520 13:52:56.208317 335654912 slave.cpp:724] Got assigned task 
> Task_Tracker_4 for framework 201305201352-4270135724-56831-2789-0000
> I0520 13:52:56.208647 336191488 hierarchical_allocator_process.hpp:497] 
> Framework 201305201352-4270135724-56831-2789-0000 filtered slave 
> 201305201352-4270135724-56831-2789-0 for 5.000000000000000secs
> I0520 13:52:56.208945 335118336 gc.cpp:84] Unscheduling 
> '/tmp/mesos/0/slaves/201305201352-4270135724-56831-2789-0/frameworks/201305201352-4270135724-56831-2789-0000'
>  for removal
> I0520 13:52:56.209274 336191488 slave.cpp:822] Launching task Task_Tracker_4 
> for framework 201305201352-4270135724-56831-2789-0000
> I0520 13:52:56.215672 336191488 paths.hpp:302] Created executor directory 
> '/tmp/mesos/0/slaves/201305201352-4270135724-56831-2789-0/frameworks/201305201352-4270135724-56831-2789-0000/executors/executor_Task_Tracker_4/runs/8b73d7c3-edb7-4714-a54a-b042c5183063'
> I0520 13:52:56.215981 336191488 slave.cpp:933] Queuing task 'Task_Tracker_4' 
> for executor executor_Task_Tracker_4 of framework 
> '201305201352-4270135724-56831-2789-0000
> I0520 13:52:56.215989 336728064 process_isolator.cpp:120] Launching 
> executor_Task_Tracker_4 
> (/Users/vinod/workspace/apache/mesos/build/hadoop/hadoop-0.20.205.0/bin/mesos-executor)
>  in 
> /tmp/mesos/0/slaves/201305201352-4270135724-56831-2789-0/frameworks/201305201352-4270135724-56831-2789-0000/executors/executor_Task_Tracker_4/runs/8b73d7c3-edb7-4714-a54a-b042c5183063
>  with resources cpus=1; mem=1280' for framework 
> 201305201352-4270135724-56831-2789-0000
> I0520 13:52:56.216097 336191488 slave.cpp:517] Successfully attached file 
> '/tmp/mesos/0/slaves/201305201352-4270135724-56831-2789-0/frameworks/201305201352-4270135724-56831-2789-0000/executors/executor_Task_Tracker_4/runs/8b73d7c3-edb7-4714-a54a-b042c5183063'
> I0520 13:52:56.218552 336728064 process_isolator.cpp:182] Forked executor at 
> 3068
> Failed to determine the canonical path 
> '/usr/local/libexec/mesos/mesos-launcher' for the mesos-launcher: No such 
> file or directory
> W0520 13:52:57.182904 335118336 master.cpp:82] No whitelist given. 
> Advertising offers for all slaves

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to