[ https://issues.apache.org/jira/browse/YARN-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325069#comment-14325069 ]
Hadoop QA commented on YARN-3132: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12698572/YARN-3132.1.patch against trunk revision 043e44b. {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:red}-1 findbugs{color}. The patch appears to introduce 5 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:red}-1 core tests{color}. The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestSchedulingPolicy The following test timeouts occurred in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart Test results: https://builds.apache.org/job/PreCommit-YARN-Build/6652//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-YARN-Build/6652//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6652//console This message is automatically generated. > RMNodeLabelsManager should remove node from node-to-label mapping when node > becomes deactivated > ----------------------------------------------------------------------------------------------- > > Key: YARN-3132 > URL: https://issues.apache.org/jira/browse/YARN-3132 > Project: Hadoop YARN > Issue Type: Sub-task > Components: api, client, resourcemanager > Reporter: Wangda Tan > Assignee: Wangda Tan > Attachments: YARN-3132.1.patch > > > Using an example to explain: > 1) Admin specify host1 has label=x > 2) node=host1:123 registered > 3) Get node-to-label mapping, return host1/host1:123 > 4) node=host1:123 unregistered > 5) Get node-to-label mapping, still returns host1:123 > Probably we should remove host1:123 when it becomes deactivated and no > directly label assigned to it (directly assign means admin specify host1:123 > has x instead of host1 has x). -- This message was sent by Atlassian JIRA (v6.3.4#6332)