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 "Subru Krishnan (JIRA)" <ji...@apache.org> on 2016/10/12 01:16:20 UTC
[jira] [Assigned] (YARN-5711) AM cannot reconnect to RM after
failover when using RequestHedgingRMFailoverProxyProvider
[ https://issues.apache.org/jira/browse/YARN-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Subru Krishnan reassigned YARN-5711:
------------------------------------
Assignee: Subru Krishnan
> AM cannot reconnect to RM after failover when using RequestHedgingRMFailoverProxyProvider
> -----------------------------------------------------------------------------------------
>
> Key: YARN-5711
> URL: https://issues.apache.org/jira/browse/YARN-5711
> Project: Hadoop YARN
> Issue Type: Bug
> Components: applications, resourcemanager
> Affects Versions: 2.9.0, 3.0.0-alpha1
> Reporter: Subru Krishnan
> Assignee: Subru Krishnan
> Priority: Critical
>
> When RM failsover, it does _not_ auto re-register running apps and so they need to re-register when reconnecting to new primary. This is done by catching {{ApplicationMasterNotRegisteredException}} in *allocate* calls and re-registering. But *RequestHedgingRMFailoverProxyProvider* does _not_ propagate {{YarnException}} as the actual invocation is done asynchronously using seperate threads, so AMs cannot reconnect to RM after failover.
> This JIRA proposes that the *RequestHedgingRMFailoverProxyProvider* propagate any {{YarnException}} that it encounters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org