You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Qian Zhang (JIRA)" <ji...@apache.org> on 2018/05/04 09:33:00 UTC
[jira] [Commented] (MESOS-8876) Normal exit of Docker container
using rexray volume results in TASK_FAILED
[ https://issues.apache.org/jira/browse/MESOS-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463620#comment-16463620 ]
Qian Zhang commented on MESOS-8876:
-----------------------------------
https://reviews.apache.org/r/66947/
> Normal exit of Docker container using rexray volume results in TASK_FAILED
> --------------------------------------------------------------------------
>
> Key: MESOS-8876
> URL: https://issues.apache.org/jira/browse/MESOS-8876
> Project: Mesos
> Issue Type: Bug
> Components: docker
> Reporter: Qian Zhang
> Assignee: Qian Zhang
> Priority: Major
> Attachments: task_exit_volume.json
>
>
> In the fix to MESOS-8488, we reap the Docker container process directly in Docker executor, and it will wait for `docker run` to return for at most 3 seconds. However, in some cases, the `docker run` command will indeed need more than 3 seconds to return, e.g., the Docker container uses an external rexray volume (see the attached task json as an example), for such container, there will be about 5 seconds between container process exits and the `docker run` returns (I suspect Docker daemon was doing some stuff related to rexray volume during this time), so we will reap this container, and send a {{TASK_FAILED}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)