[
https://issues.apache.org/jira/browse/YARN-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738599#comment-15738599
]
Konstantinos Karanasos commented on YARN-5216:
----------------------------------------------
bq. Given the fact that the actual container executor executable binary that is
deployed on the cluster can be decided by the cluster admin and the admin can
choose to deploy an executor + runtime combo that supports pausing/freezing or
not, I am wondering if a conf/knob to determine if the scheduler should
pause/kill a container might seem superfluous in that case.
Hey guys, regarding this, I think we should have a parameter for the pausing
vs. killing.
Even if an executor supports pausing, the admin might want to not pause
containers, but kill them instead.
Otherwise, to achieve this behavior, we will need to have two implementations
of each executor: one that kills containers and one that preempts.
> Expose configurable preemption policy for OPPORTUNISTIC containers running on
> the NM
> ------------------------------------------------------------------------------------
>
> Key: YARN-5216
> URL: https://issues.apache.org/jira/browse/YARN-5216
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: distributed-scheduling
> Reporter: Arun Suresh
> Assignee: Hitesh Sharma
> Labels: oct16-hard
> Attachments: YARN-5216-YARN-5972.001.patch, YARN5216.001.patch,
> yarn5216.002.patch
>
>
> Currently, the default action taken by the QueuingContainerManager,
> introduced in YARN-2883, when a GUARANTEED Container is scheduled on an NM
> with OPPORTUNISTIC containers using up resources, is to KILL the running
> OPPORTUNISTIC containers.
> This JIRA proposes to expose a configurable hook to allow the NM to take a
> different action.
--
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
