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 "Bikas Saha (JIRA)" <ji...@apache.org> on 2013/10/03 23:12:46 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 ]

Bikas Saha updated MAPREDUCE-5559:
----------------------------------

    Summary: Reconsidering the policy of ignoring the blacklist after reaching the threshold  (was: Reconsidering the policy of ignoring the blacklist after reaching the thread)

> 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
>            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.1#6144)