Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 2 Dec 2016 03:21:58 +0000 (UTC)
From: "Hitesh Sharma (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12982533.1466730366000.419765.1480648918773@Atlassian.JIRA>
In-Reply-To: <JIRA.12982533.1466730366000@Atlassian.JIRA>
References: <JIRA.12982533.1466730366000@Atlassian.JIRA> <JIRA.12982533.1466730366218@arcas>
Subject: [jira] [Comment Edited] (YARN-5292) Support for PAUSED container
 state
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 02 Dec 2016 03:22:00 -0000


    [ https://issues.apache.org/jira/browse/YARN-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713883#comment-15713883 ] 

Hitesh Sharma edited comment on YARN-5292 at 12/2/16 3:21 AM:
--------------------------------------------------------------

[~asuresh], can you please look at the attached patch? Thanks!


was (Author: hrsharma):
[~asuresh]], can you please look at the attached patch? Thanks!

> Support for PAUSED container state
> ----------------------------------
>
>                 Key: YARN-5292
>                 URL: https://issues.apache.org/jira/browse/YARN-5292
>             Project: Hadoop YARN
>          Issue Type: New Feature
>            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.pdf
>
>
> 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. 
>  


--
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