[ https://issues.apache.org/jira/browse/YARN-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738072#comment-15738072 ]
Arun Suresh commented on YARN-5216: ----------------------------------- Thanks for working on this [~hrsharma] I just kicked jenkins again, for some reason it didnt pick your patch... it looks fine now Just took a pass at your patch. I was wondering if in the Scheduler, instead of deciding explicitly based on configuration whether to kill or pause, it should just call a preempt method. Then if the ContainerExecutor + Runtime supports pausing, it will pause the container and send a CONTAINER_PAUSED event to the scheduler, else if it does not support pause/freezing, it will kill the container and send CONTAINER_KILLED once it is killed. > 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