You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Tao Jie (JIRA)" <ji...@apache.org> on 2017/02/17 02:08:41 UTC
[jira] [Commented] (YARN-5829) FS preemption should reserve a node
before considering containers on it for preemption
[ https://issues.apache.org/jira/browse/YARN-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871054#comment-15871054 ]
Tao Jie commented on YARN-5829:
-------------------------------
[~kasha], it seems similar situation as mentioned in YARN-5636.
Should we have a common mechanism that supports "reserving certain resource on a certain node for a certain app for a while" ?
> FS preemption should reserve a node before considering containers on it for preemption
> --------------------------------------------------------------------------------------
>
> Key: YARN-5829
> URL: https://issues.apache.org/jira/browse/YARN-5829
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: fairscheduler
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
>
> FS preemption evaluates nodes for preemption, and subsequently preempts identified containers. If this node is not reserved for a specific application, any other application could be allocated resources on this node.
> Reserving the node for the starved application before preempting containers would help avoid this.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org