[
https://issues.apache.org/jira/browse/YARN-7587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272593#comment-16272593
]
Weiwei Yang commented on YARN-7587:
-----------------------------------
This is based on the discussion from [this
comment|https://issues.apache.org/jira/browse/YARN-2889?focusedCommentId=16271444&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16271444]
in YARN-2889. Ping [~asuresh], please help to review.
bq. To be honest, instead of a total sort, a partial sorting of nodes which
includes only nodes whose queue length < x, where x is a small value to give a
higher probably for the O container to run
v1 patch is not using this approach, I am not sure what could be the reasonable
value for x, it could be very different case by case. So I just exclude nodes
whose queue is full, like v1 patch prompted. Please let me know if this works
for you.
Thanks
> 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]
