Gilbert Song edited comment on MESOS-8565 at 2/14/18 6:41 PM:

commit 9d4c6d9576741cc480c75f8e59cc8d1adc9849fc

Author: Qian Zhang <zhq527...@gmail.com>

Date:   Wed Feb 14 00:17:37 2018 -0800


    Attached/detached volume directory for task which has volume specified.


    Review: [https://reviews.apache.org/r/65570/]

was (Author: gilbert):
commit a7714536fad1140fd0c07c47e32b40e9ed00a3c3

Author: Qian Zhang <zhq527...@gmail.com>

Date:   Mon Feb 5 20:42:07 2018 +0800


    Reaped the container process directly in Docker executor.


    Due to a Docker issue (https://github.com/moby/moby/issues/33820),

    Docker daemon can fail to catch a container exit, i.e., the container

    process has already exited but the command `docker ps` shows the

    container still running, this will lead to the "docker run" command

    that we execute in Docker executor never returning, and it will also

    cause the `docker stop` command takes no effect, i.e., it will return

    without error but `docker ps` shows the container still running, so

    the task will stuck in `TASK_KILLING` state.


    To workaround this Docker issue, in this patch we made Docker executor

    reaps the container process directly so Docker executor will be notified

    once the container process exits.


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

> Persistent volumes are not visible in Mesos UI when launching a pod using 
> default executor.
> -------------------------------------------------------------------------------------------
>                 Key: MESOS-8565
>                 URL: https://issues.apache.org/jira/browse/MESOS-8565
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 1.2.2, 1.3.1, 1.4.1
>            Reporter: Qian Zhang
>            Assignee: Qian Zhang
>            Priority: Major
>             Fix For: 1.6.0, 1.5.1
> When user launches a pod to use a persistent volume in DC/OS, the nested 
> containers in the pod can access the PV successfully and the PV directory of 
> the executor shown in Mesos UI has all the contents written by the tasks, but 
> the PV directory of the tasks shown in DC/OS UI and Mesos UI is empty.

This message was sent by Atlassian JIRA

Reply via email to