[
https://issues.apache.org/jira/browse/MAPREDUCE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785557#comment-13785557
]
Hudson commented on MAPREDUCE-5489:
-----------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #4527 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/4527/])
MAPREDUCE-5489. MR jobs hangs as it does not use the node-blacklisting feature
in RM requests (Zhijie Shen via bikas) (bikas:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1529005)
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerRequestor.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestRMContainerAllocator.java
> 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
> Priority: Critical
> Fix For: 2.1.2-beta
>
> Attachments: MAPREDUCE-5489.1.patch, MAPREDUCE-5489.2.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)
