[
https://issues.apache.org/jira/browse/YARN-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626273#comment-16626273
]
Hudson commented on YARN-8696:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15042 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/15042/])
YARN-8696. [AMRMProxy] FederationInterceptor upgrade: home sub-cluster (gifuma:
rev 3090922805699b8374a359e92323884a4177dc4e)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/src/main/java/org/apache/hadoop/yarn/server/uam/UnmanagedAMPoolManager.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/src/main/java/org/apache/hadoop/yarn/server/AMHeartbeatRequestHandler.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/amrmproxy/TestFederationInterceptor.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ApplicationMasterService.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/src/main/java/org/apache/hadoop/yarn/server/uam/UnmanagedApplicationManager.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/client/AMRMClientUtils.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/amrmproxy/FederationInterceptor.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/amrmproxy/TestableFederationInterceptor.java
* (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/test/java/org/apache/hadoop/yarn/server/MockResourceManagerFacade.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/src/main/java/org/apache/hadoop/yarn/server/federation/utils/FederationRegistryClient.java
> [AMRMProxy] FederationInterceptor upgrade: home sub-cluster heartbeat async
> ---------------------------------------------------------------------------
>
> Key: YARN-8696
> URL: https://issues.apache.org/jira/browse/YARN-8696
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager
> Reporter: Botong Huang
> Assignee: Botong Huang
> Priority: Major
> Fix For: 3.2.0
>
> Attachments: YARN-8696-branch-2.v6.patch, YARN-8696.v1.patch,
> YARN-8696.v2.patch, YARN-8696.v3.patch, YARN-8696.v4.patch,
> YARN-8696.v5.patch, YARN-8696.v6.patch
>
>
> Today in _FederationInterceptor_, the heartbeat to home sub-cluster is
> synchronous. After the heartbeat is sent out to home sub-cluster, it waits
> for the home response to come back before merging and returning the (merged)
> heartbeat result to back AM. If home sub-cluster is suffering from connection
> issues, or down during an YarnRM master-slave switch, all heartbeat threads
> in _FederationInterceptor_ will be blocked waiting for home response. As a
> result, the successful UAM heartbeats from secondary sub-clusters will not be
> returned to AM at all. Additionally, because of the fact that we kept the
> same heartbeat responseId between AM and home RM, lots of tricky handling are
> needed regarding the responseId resync when it comes to
> _FederationInterceptor_ (part of AMRMProxy, NM) work preserving restart
> (YARN-6127, YARN-1336), home RM master-slave switch etc.
> In this patch, we change the heartbeat to home sub-cluster to asynchronous,
> same as the way we handle UAM heartbeats in secondaries. So that any
> sub-cluster down or connection issues won't impact AM getting responses from
> other sub-clusters. The responseId is also managed separately for home
> sub-cluster and AM, and they increment independently. The resync logic
> becomes much cleaner.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
