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

Timothy Chen closed MESOS-2583.
-------------------------------
    Resolution: Fixed

commit 00318fc1b30fc0961c2dfa4d934c37866577d801
Author: Timothy Chen <tnac...@apache.org>
Date:   Wed Apr 1 16:56:53 2015 -0700

    Add test to verify executor clean up in docker containerizer.

    Review: https://reviews.apache.org/r/32798

commit 879044096f80adb1799ce43acc1fc5ae58dfac69
Author: Timothy Chen <tnac...@apache.org>
Date:   Wed Apr 1 16:29:54 2015 -0700

    Kill the executor when docker container is destroyed.

    Review: https://reviews.apache.org/r/32797

commit 591d1090f69a7d9197aea355488c973c41881be7
Author: Timothy Chen <tnac...@apache.org>
Date:   Wed Apr 1 16:03:43 2015 -0700

    Only update docker container when resources differs.

    Review: https://reviews.apache.org/r/32796

> Tasks getting stuck in staging
> ------------------------------
>
>                 Key: MESOS-2583
>                 URL: https://issues.apache.org/jira/browse/MESOS-2583
>             Project: Mesos
>          Issue Type: Bug
>          Components: slave
>    Affects Versions: 0.22.0
>            Reporter: Brenden Matthews
>            Assignee: Timothy Chen
>         Attachments: 
> Justin-Bieber_The-Beliebers-Want-to-Believe-2-650x406.jpg, Screen Shot 
> 2015-03-26 at 11.59.33 AM.png, Screen Shot 2015-03-30 at 2.04.14 PM.png, 
> log.txt
>
>
> Tasks occasionally become stuck in the `TASK_STAGING` state after launching. 
> It appears that this affects both Docker and non-Docker tasks, especially 
> those which start up and fail immediately. Attached is a sample of the slave 
> log as well as screenshots from a testing cluster showing the tasks which are 
> stuck in staging, and then a number of failed tasks which occurs after 
> restarting the slave process. Justin Bieber is provided for scale.
> This may be related to MESOS-1837, and quite possibly the same issue, but it 
> remains unclear.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to