[
https://issues.apache.org/jira/browse/YARN-7587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273572#comment-16273572
]
Arun Suresh commented on YARN-7587:
-----------------------------------
Thanks for the patch [~cheersyang].
Rather than performing an extra iteration to filter the list, maybe it might be
better to modify the {{getMetric}} method in the comparator to return MAX_INT /
MIN_INT where appropriate if the isQueueFull is true for the clusternode ?
Also was thinking, we should do the same for de-comissioned nodes as well.
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
