[
https://issues.apache.org/jira/browse/YARN-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348557#comment-15348557
]
Hitesh Sharma edited comment on YARN-5292 at 6/24/16 10:33 PM:
---------------------------------------------------------------
[~jlowe] and [~asuresh], appreciate the feedback.
It's a good idea to have the "PAUSING" state. If the container fails to pause
then we proceed to kill and terminate it. How the pausing is implemented is
specific to the container so I'm not so sure if we need APIs to store state.
Thanks again for the feedback.
was (Author: hrsharma):
[~Jason Lowe] and [~Arun Suresh], appreciate the feedback.
It's a good idea to have the "PAUSING" state. If the container fails to pause
then we proceed to kill and terminate it. How the pausing is implemented is
specific to the container so I'm not so sure if we need APIs to store state.
Thanks again for the feedback.
> 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
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
