[
https://issues.apache.org/jira/browse/YARN-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364799#comment-15364799
]
Konstantinos Karanasos commented on YARN-5216:
----------------------------------------------
Thinking more about it...
Another option would be to create a class
{{QueuingContainersPreemptionManagerImpl}} that subclasses the
{{QueuingContainersManagerImpl}}.
This way you don't need to touch the {{QueuingContainersManagerImpl}} (which
will provide the default option of killing containers), and you can override
any of the methods you need (e.g., stopContainer) in the subclass.
That will give you the flexibility to directly access any of the fields of the
{{QueuingContainersManagerImpl}} in your subclass.
> 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: Bug
> Reporter: Arun Suresh
> Assignee: Hitesh Sharma
> Attachments: 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
