Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 2 Feb 2012 11:41:53 +0000 (UTC)
From: "Harsh J (Updated) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <2007706028.2177.1328182913402.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2086034356.1975.1328177273855.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-3789) CapacityTaskScheduler may perform
 unnecessary reservations in heterogenous tracker environments
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Harsh J updated MAPREDUCE-3789:
-------------------------------

    Attachment: MAPREDUCE-3789.patch
    
> CapacityTaskScheduler may perform unnecessary reservations in heterogenous tracker environments
> -----------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3789
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3789
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 1.1.0
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Critical
>         Attachments: MAPREDUCE-3789.patch, MAPREDUCE-3789.patch
>
>
> Briefly, to reproduce:
> * Run JT with CapacityTaskScheduler [Say, Cluster max map = 8G, Cluster map = 2G]
> * Run two TTs but with varied capacity, say, one with 4 map slot, another with 3 map slots.
> * Run a job with two tasks, each demanding mem worth 4 slots at least (Map mem = 7G or so).
> * Job will begin running on TT #1, but will also end up reserving the 3 slots on TT #2 cause it does not check for the maximum limit of slots when reserving (as it goes greedy, and hopes to gain more slots in future).
> * Other jobs that could've run on the TT #2 over 3 slots are thereby blocked out due to this illogical reservation.
> I've not yet tested MR2 for this so feel free to weigh in if it affects MR2 as well.
> For MR1, I've attached a test case initially to indicate this. A fix that checks reservations vs. max slots, to follow.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira