You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Botong Huang (JIRA)" <ji...@apache.org> on 2018/10/01 15:59:00 UTC
[jira] [Commented] (YARN-8760) [AMRMProxy] Fix concurrent
re-register due to YarnRM failover in AMRMClientRelayer
[ https://issues.apache.org/jira/browse/YARN-8760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634229#comment-16634229 ]
Botong Huang commented on YARN-8760:
------------------------------------
TestNMProxy failure is irrelevant and is tracked under YARN-8837
> [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
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org