Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 6 Dec 2016 15:39:59 +0000 (UTC)
From: "Arun Suresh (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12982533.1466730366000.451360.1481038799103@Atlassian.JIRA>
In-Reply-To: <JIRA.12982533.1466730366000@Atlassian.JIRA>
References: <JIRA.12982533.1466730366000@Atlassian.JIRA> <JIRA.12982533.1466730366218@arcas>
Subject: [jira] [Updated] (YARN-5292) NM Container lifecycle and state
 transitions to support for PAUSED container state.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 06 Dec 2016 15:40:01 -0000


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

Arun Suresh updated YARN-5292:
------------------------------
    Description: This JIRA addresses the NM Container and state machine and lifecycle changes needed  to support pausing.  (was: YARN-2877 introduced OPPORTUNISTIC containers, and YARN-5216 proposes to add capability to customize how OPPORTUNISTIC containers get preempted.

In this JIRA we propose introducing a PAUSED container state.
When a running container gets preempted, it enters the PAUSED state, where it remains until resources get freed up on the node then the preempted container can resume to the running state.
 
One scenario where this capability is useful is work preservation. How preemption is done, and whether the container supports it, is implementation specific.

For instance, if the container is a virtual machine, then preempt would pause the VM and resume would restore it back to the running state.
If the container doesn't support preemption, then preempt would default to killing the container. 
 )

> NM Container lifecycle and state transitions to support for PAUSED container state.
> -----------------------------------------------------------------------------------
>
>                 Key: YARN-5292
>                 URL: https://issues.apache.org/jira/browse/YARN-5292
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Hitesh Sharma
>            Assignee: Hitesh Sharma
>         Attachments: YARN-5292.001.patch, YARN-5292.002.patch, YARN-5292.003.patch, YARN-5292.004.patch, YARN-5292.005.patch, yarn-5292.pdf
>
>
> This JIRA addresses the NM Container and state machine and lifecycle changes needed  to support pausing.


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

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