hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5711) AM cannot reconnect to RM after failover when using RequestHedgingRMFailoverProxyProvider
Date Fri, 21 Oct 2016 01:48:58 GMT

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

Hadoop QA commented on YARN-5711:
---------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s {color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 6s {color} | {color:red}
YARN-5711 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12834588/YARN-5711-v1.patch
|
| JIRA Issue | YARN-5711 |
| Console output | https://builds.apache.org/job/PreCommit-YARN-Build/13461/console |
| Powered by | Apache Yetus 0.3.0   http://yetus.apache.org |


This message was automatically generated.



> 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
>         Attachments: YARN-5711-v1.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
(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


Mime
View raw message