[
https://issues.apache.org/jira/browse/YARN-8760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634611#comment-16634611
]
Hudson commented on YARN-8760:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15085 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/15085/])
YARN-8760. [AMRMProxy] Fix concurrent re-register due to YarnRM failover
(gifuma: rev 59d5af21b7a8f52e8c89cbc2d25fe3d449b2657a)
* (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-common/src/main/java/org/apache/hadoop/yarn/server/AMRMClientRelayer.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/src/test/java/org/apache/hadoop/yarn/server/TestAMRMClientRelayer.java
> [AMRMProxy] Fix concurrent re-register due to YarnRM failover in
> AMRMClientRelayer
> ----------------------------------------------------------------------------------
>
> Key: YARN-8760
> URL: https://issues.apache.org/jira/browse/YARN-8760
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Botong Huang
> Assignee: Botong Huang
> Priority: Major
> Fix For: 3.2.0
>
> Attachments: YARN-8760.v1.patch
>
>
> When home YarnRM is failing over, FinishApplicationMaster call from AM can
> have multiple retry threads outstanding in FederationInterceptor. When new
> YarnRM come back up, all retry threads will re-register to YarnRM. The first
> one will succeed but the rest will get "Application Master is already
> registered" exception. We should catch and swallow this exception and move
> on.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
