Hi Qian, State 5 is TASK_LOST. Can you take a look at the executor logs? I have seen this before for the test frameworks when they can't locate libmesos.so or the executor binary.
Cheers, Niklas On 20 August 2014 01:11, Qian Zhang <[email protected]> wrote: > Hi All, > > I am trying mesos-0.19.1, and when I ran " ./src/test-framework --master= > 192.168.122.5:5050" (192.168.122.5 is my mesos master's IP, and I was > also running ./src/test-framework on mesos master), I found it just can not > finish: > > [root@mesos1 build]# ./src/test-framework --master=192.168.122.5:5050 > I0820 15:31:02.603349 21797 sched.cpp:126] Version: 0.19.1 > I0820 15:31:02.612529 21817 sched.cpp:222] New master detected at > [email protected]:5050 > I0820 15:31:02.613699 21817 sched.cpp:230] No credentials provided. > Attempting to register without authentication > I0820 15:31:02.618561 21817 sched.cpp:397] Framework registered with > 20140820-152819-91924672-5050-21680-0000 > Registered! > .Starting task 0 on mesos1 > Starting task 1 on mesos1 > Starting task 2 on mesos1 > Starting task 3 on mesos1 > W0820 15:31:02.623677 21822 sched.cpp:901] Attempting to launch task 1 > with an unknown offer 20140820-152819-91924672-5050-21680-0 > W0820 15:31:02.623733 21822 sched.cpp:901] Attempting to launch task 2 > with an unknown offer 20140820-152819-91924672-5050-21680-0 > W0820 15:31:02.623759 21822 sched.cpp:901] Attempting to launch task 3 > with an unknown offer 20140820-152819-91924672-5050-21680-0 > Task 0 is in state 5 > Task 1 is in state 5 > Task 2 is in state 5 > Task 3 is in state 5 > .Starting task 4 on mesos1 > Task 4 is in state 5 > > .................................................................................................................... > > It last a long time ... > > Any ideas about what happened? > > > Thanks, > Qian > > >
