hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5711) Propogate exceptions back to client when using hedging RM failover provider
Date Tue, 25 Oct 2016 02:20:59 GMT

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

Hudson commented on YARN-5711:

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10669 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/10669/])
YARN-5711. Propogate exceptions back to client when using hedging RM (subru: rev 0a166b13472213db0a0cd2dfdaddb2b1746b3957)
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/client/RequestHedgingRMFailoverProxyProvider.java
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/TestHedgingRequestRMFailoverProxyProvider.java

> Propogate exceptions back to client when using hedging RM failover provider
> ---------------------------------------------------------------------------
>                 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
>             Fix For: 2.9.0, 3.0.0-alpha2
>         Attachments: YARN-5711-v1.patch, YARN-5711-v2.patch, YARN-5711.v1.1.patch
> 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

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

View raw message