[
https://issues.apache.org/jira/browse/YARN-5972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Suresh updated YARN-5972:
------------------------------
Description:
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.
Instead of preempting a running container, the container can be moved to a
PAUSED state, where it remains until resources get freed up on the node then
the preempted container can resume to the running state.
Note that process freezing this is already supported by 'cgroups freezer' which
is used internally by the docker pause functionality. Windows also has OS level
support of a similar nature.
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 call would
pause the VM and resume would restore it back to the running state.
If the container executor / runtime doesn't support preemption, then preempt
would default to killing the container.
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.
Instead of preempting a running container, the container can be moved to a
PAUSED state, where it remains until resources get freed up on the node then
the preempted container can resume to the running state.
Note that process freezing this is already supported by 'cgroups freezer' which
is used internally by the docker pause functionality. Windows also has OS level
support of a similar nature.
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.
> Add Support for Pausing/Freezing of containers
> ----------------------------------------------
>
> Key: YARN-5972
> URL: https://issues.apache.org/jira/browse/YARN-5972
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Arun Suresh
>
> 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.
> Instead of preempting a running container, the container can be moved to a
> PAUSED state, where it remains until resources get freed up on the node then
> the preempted container can resume to the running state.
> Note that process freezing this is already supported by 'cgroups freezer'
> which is used internally by the docker pause functionality. Windows also has
> OS level support of a similar nature.
> 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 call would
> pause the VM and resume would restore it back to the running state.
> If the container executor / runtime 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
