[
https://issues.apache.org/jira/browse/YARN-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738398#comment-15738398
]
Hitesh Sharma commented on YARN-5216:
-------------------------------------
Hi [~asuresh], are you saying that we add a preempt method in the container
executor and have the scheduler call that instead?
One issue with that approach is that we need to add a conf knob in the executor
to pick the kind of preemption you want and that also becomes a little too
generic and ambiguous. What we are looking for is preemption of opp. container
to schedule a guaranteed one and I feel that's best captured in the scheduler
state.
LMK your thoughts.
> 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: [email protected]
For additional commands, e-mail: [email protected]
