[
https://issues.apache.org/jira/browse/YARN-7587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273547#comment-16273547
]
Konstantinos Karanasos commented on YARN-7587:
----------------------------------------------
+1 for this optimization -- I think it will help a lot.
By a quick look at the patch, it looks reasonable.
We can explain a bit more in comments the different max queue lengths, as it
will end up being confusing to have the limit set by the RM (calculated by the
QueueLimitCalculator) and the max length set by each NM.
> Skip dispatching opportunistic containers to nodes whose queue is already full
> ------------------------------------------------------------------------------
>
> Key: YARN-7587
> URL: https://issues.apache.org/jira/browse/YARN-7587
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 2.9.0
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Attachments: YARN-7587.001.patch
>
>
> When there is a lot of opportunistic container requests, even if NM queue is
> full, RM continues to dispatch O containers to that node. Such allocations
> will be killed immediately by NM causing a waste of resource. Propose to
> exclude such nodes in the load monitor.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
