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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/09/28 20:56:04 UTC

[jira] [Updated] (MAPREDUCE-5559) Reconsidering the policy of ignoring the blacklist after reaching the threshold

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

Vinod Kumar Vavilapalli updated MAPREDUCE-5559:
-----------------------------------------------
    Fix Version/s:     (was: 2.4.0)

Dropping fix-version.

> Reconsidering the policy of ignoring the blacklist after reaching the threshold
> -------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5559
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5559
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 2.1.1-beta
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>
> Nowadays, when MR AM find the number of blacklisted nodes reaches one threshold, the blacklist will be totally ignored. The newly assigned containers on the blacklisted nodes will be allocated. This may be not the best practice. We need to reconsider of it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)