[
https://issues.apache.org/jira/browse/YARN-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763587#comment-15763587
]
Arun Suresh commented on YARN-5216:
-----------------------------------
Thanks for updating the patch [~hrsharma]
Couple of comments:
# In the ContainerScheduler, rename onContainerCompleted() method to
onResourcesReclaimed(). Think that might make more sense now.
# Instead of explicitly calling "dispatcher.getEventHandler().handle(..)" from
within ContainerScheduler, can you create a method inside Container:
sendPauseEvent(String) and sendResumeEvent(String)
# Actually w.r.t the above comment, consider just updating the
sendLaunchEvent() method that is already present to check the container state,
and if paused, send the pause event else send the launch event to the launcher.
> 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,
> YARN-5216-YARN-5972.002.patch, YARN-5216-YARN-5972.003.patch,
> YARN-5216-YARN-5972.004.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]
