You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Hitesh Sharma (JIRA)" <ji...@apache.org> on 2016/08/04 21:17:20 UTC

[jira] [Updated] (YARN-5292) Support for PAUSED container state

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

Hitesh Sharma updated YARN-5292:
--------------------------------
    Attachment: yarn-5292.pdf

Please find the attached document that describes some of the design and implementation details of adding PAUSE and RESUME states to YARN containers.

Appreciate the feedback and comments.

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