[ https://issues.apache.org/jira/browse/MAPREDUCE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784701#comment-13784701 ]
Hadoop QA commented on MAPREDUCE-5489: -------------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12606496/MAPREDUCE-5489.1.patch against trunk revision . {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}. 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-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4080//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4080//console This message is automatically generated. > MR jobs hangs as it does not use the node-blacklisting feature in RM requests > ----------------------------------------------------------------------------- > > Key: MAPREDUCE-5489 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5489 > Project: Hadoop Map/Reduce > Issue Type: Bug > Reporter: Yesha Vora > Assignee: Zhijie Shen > Attachments: MAPREDUCE-5489.1.patch > > > When RM restarted, if during restart one NM went bad (bad disk), NM got > blacklisted by AM and RM keeps giving the containers on the same node even > though AM doesn't want it there. > Need to change AM to specifically blacklist node in the RM requests. -- This message was sent by Atlassian JIRA (v6.1#6144)