Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 3 Oct 2013 20:44:42 +0000 (UTC)
From: "Zhijie Shen (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12672212.1380833044736.8895.1380833082739@arcas>
In-Reply-To: <JIRA.12672212.1380833044736@arcas>
References: <JIRA.12672212.1380833044736@arcas>
Subject: [jira] [Created] (MAPREDUCE-5559) Reconsidering the policy of
 ignoring the blacklist after reaching the thread
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Zhijie Shen created MAPREDUCE-5559:
--------------------------------------

             Summary: Reconsidering the policy of ignoring the blacklist after reaching the thread
                 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 RM 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)