[
https://issues.apache.org/jira/browse/YARN-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784692#comment-13784692
]
Hadoop QA commented on YARN-1265:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12606495/YARN-1265.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
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 1.3.9) 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/2069//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2069//console
This message is automatically generated.
> Fair Scheduler chokes on unhealthy node reconnect
> -------------------------------------------------
>
> Key: YARN-1265
> URL: https://issues.apache.org/jira/browse/YARN-1265
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, scheduler
> Affects Versions: 2.1.1-beta
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: YARN-1265.patch
>
>
> Only nodes in the RUNNING state are tracked by schedulers. When a node
> reconnects, RMNodeImpl.ReconnectNodeTransition tries to remove it, even if
> it's in the RUNNING state. The FairScheduler doesn't guard against this.
> I think the best way to fix this is to check to see whether a node is RUNNING
> before telling the scheduler to remove it.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
