[
https://issues.apache.org/jira/browse/YARN-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746109#comment-15746109
]
Miklos Szegedi commented on YARN-5216:
--------------------------------------
[~asuresh], [~hrsharma]
Since I was asked, I do not have strong opinion about this issue. I think it is
good to have a rule that one functionality is enabled only by one setting,
otherwise we increase configuration costs to the admins with testing,
troubleshooting. I think [~hrsharma]'s last suggestion having a preempt API in
container executor, which has a knob to allow KILL vs PAUSE is the closest to
what I would choose. [~asuresh], this is similar to your suggestion, isn't it?
In general it also depends on the implementation details what the administrator
wants to choose. It may be application dependent, how fast a guaranteed
application needs to start up. For example the cost of PAUSE in time is higher,
since the memory eventually needs to be written to disk, while KILL is very
fast releasing the resources right away.
> 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, 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]
