[
https://issues.apache.org/jira/browse/YARN-8581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586548#comment-16586548
]
Hudson commented on YARN-8581:
------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #14806 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14806/])
YARN-8581. [AMRMProxy] Add sub-cluster timeout in (gifuma: rev
e0f6ffdbad6f43fd43ec57fb68ebf5275b8b9ba0)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/test/java/org/apache/hadoop/yarn/conf/TestYarnConfigurationFields.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/src/main/java/org/apache/hadoop/yarn/server/federation/utils/FederationStateStoreFacade.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/src/test/java/org/apache/hadoop/yarn/server/federation/utils/FederationPoliciesTestUtil.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/src/test/java/org/apache/hadoop/yarn/server/federation/policies/amrmproxy/TestLocalityMulticastAMRMProxyPolicy.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/src/main/java/org/apache/hadoop/yarn/server/federation/policies/amrmproxy/LocalityMulticastAMRMProxyPolicy.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
> [AMRMProxy] Add sub-cluster timeout in LocalityMulticastAMRMProxyPolicy
> -----------------------------------------------------------------------
>
> Key: YARN-8581
> URL: https://issues.apache.org/jira/browse/YARN-8581
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: amrmproxy, federation
> Reporter: Botong Huang
> Assignee: Botong Huang
> Priority: Major
> Attachments: YARN-8581-branch-2.v2.patch, YARN-8581.v1.patch,
> YARN-8581.v2.patch
>
>
> In Federation, every time an AM heartbeat comes in,
> LocalityMulticastAMRMProxyPolicy in AMRMProxy splits the asks according to
> the list of active and enabled sub-clusters. However, if we haven't been able
> to heartbeat to a sub-cluster for some time (network issues, or we keep
> hitting some exception from YarnRM, or YarnRM master-slave switch is taking a
> long time etc.), we should consider the sub-cluster as unhealthy and stop
> routing asks there, until the heartbeat channel becomes healthy again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
