Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 8 Mar 2017 17:53:38 +0000 (UTC)
From: "Shane Kumpf (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13049334.1488995505000.14194.1488995618104@Atlassian.JIRA>
In-Reply-To: <JIRA.13049334.1488995505000@Atlassian.JIRA>
References: <JIRA.13049334.1488995505000@Atlassian.JIRA> <JIRA.13049334.1488995505043@jira-lw-us.apache.org>
Subject: [jira] [Assigned] (YARN-6305) Improve signaling of short lived
 containers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 08 Mar 2017 17:53:42 -0000


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

Shane Kumpf reassigned YARN-6305:
---------------------------------

    Assignee: Shane Kumpf

> Improve signaling of short lived containers
> -------------------------------------------
>
>                 Key: YARN-6305
>                 URL: https://issues.apache.org/jira/browse/YARN-6305
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: yarn
>            Reporter: Shane Kumpf
>            Assignee: Shane Kumpf
>
> Currently it is possible for containers to leak and remain in an exited state if a docker container is not fully started before being killed. Depending on the selected Docker storage driver, the lower bound on starting a container can be as much as three seconds (using {{docker run}}). If an implicit image pull occurs, this could be much longer.
> When a container is not fully started, the PID is not available yet. As a result, {{ContainerLaunch#cleanUpContainer}} will not signal the container as it relies on the PID. The PID is not required for docker client operations, so allowing the signaling to occur anyway appears to be appropriate.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org