[
https://issues.apache.org/jira/browse/YARN-8697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595703#comment-16595703
]
Giovanni Matteo Fumarola commented on YARN-8697:
------------------------------------------------
Thanks [~botong] . The change is straightforward.
Committed in trunk.
> LocalityMulticastAMRMProxyPolicy should fallback to random sub-cluster when
> cannot resolve resource
> ---------------------------------------------------------------------------------------------------
>
> Key: YARN-8697
> URL: https://issues.apache.org/jira/browse/YARN-8697
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Botong Huang
> Assignee: Botong Huang
> Priority: Major
> Fix For: 3.2.0
>
> Attachments: YARN-8697.v1.patch, YARN-8697.v2.patch
>
>
> Right now in LocalityMulticastAMRMProxyPolicy, whenever we cannot resolve the
> resource name (node or rack), we always route the request to home
> sub-cluster. However, home sub-cluster might not be always be ready to use
> (timed out YARN-8581) or enabled (by AMRMProxyPolicy weights). It might also
> be overwhelmed by the requests if sub-cluster resolver has some issue. In
> this Jira, we are changing it to pick a random active and enabled sub-cluster
> for resource request we cannot resolve.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
