hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giovanni Matteo Fumarola (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-8760) [AMRMProxy] Fix concurrent re-register due to YarnRM failover in AMRMClientRelayer
Date Mon, 01 Oct 2018 20:15:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-8760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634566#comment-16634566

Giovanni Matteo Fumarola commented on YARN-8760:

The change is straight-forward. 
Thanks [~botong] for that patch. Committed to Trunk.

> [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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message