You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "yeshavora (JIRA)" <ji...@apache.org> on 2013/08/31 00:57:51 UTC

[jira] [Updated] (MAPREDUCE-5489) MR Job hungs when any NM is blacklisted after RMrestart

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

yeshavora updated MAPREDUCE-5489:
---------------------------------

    Summary: MR Job hungs when any NM is blacklisted after RMrestart  (was: MR Job hungs when any node is blacklisted after RMrestart)
    
> MR Job hungs when any NM is blacklisted after RMrestart
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-5489
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5489
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: yeshavora
>            Assignee: Zhijie Shen
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira