hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5489) MR jobs hangs as it does not use the node-blacklisting feature in RM requests
Date Thu, 03 Oct 2013 18:56:49 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785439#comment-13785439
] 

Bikas Saha commented on MAPREDUCE-5489:
---------------------------------------

Typos
+ assertBlackListAddtionsAndRemovals
+    // Because makeRemoteRequest will not be ware of it until next call

In general the policy of ignoring all blacklisted nodes after the threshold is reached seems
incorrect. Lets create a follow up jira to fix that.

> 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)

Mime
View raw message