[
https://issues.apache.org/jira/browse/YARN-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139523#comment-14139523
]
Hadoop QA commented on YARN-2561:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12669786/YARN-2561-v5.patch
against trunk revision 570b8b4.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/5027//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5027//console
This message is automatically generated.
> MR job client cannot reconnect to AM after NM restart.
> ------------------------------------------------------
>
> Key: YARN-2561
> URL: https://issues.apache.org/jira/browse/YARN-2561
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Tassapol Athiapinya
> Assignee: Junping Du
> Priority: Blocker
> Attachments: YARN-2561-v2.patch, YARN-2561-v3.patch,
> YARN-2561-v4.patch, YARN-2561-v5.patch, YARN-2561.patch
>
>
> Work-preserving NM restart is disabled.
> Submit a job. Restart the only NM and found that Job will hang with connect
> retries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
