Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 8 Aug 2011 18:42:28 +0000 (UTC)
From: "Thomas Graves (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <743761490.17357.1312828948601.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1319853611.8212.1311697389563.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-2729) Reducers are always counted
 having "pending tasks" even if they can't be scheduled yet because not
 enough of their mappers have completed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081118#comment-13081118 ] 

Thomas Graves commented on MAPREDUCE-2729:
------------------------------------------

The patch is for the branch-0.20-security branch.  I will look at putting it on trunk.

> Reducers are always counted having "pending tasks" even if they can't be scheduled yet because not enough of their mappers have completed
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2729
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2729
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 0.20.205.0
>         Environment: 0.20.1xx-Secondary
>            Reporter: Sherry Chen
>            Assignee: Sherry Chen
>             Fix For: 0.20.205.0
>
>         Attachments: MAPREDUCE-2729.patch
>
>
> In capacity scheduler, number of users in a queue needing slots are calculated based on whether users' jobs have any pending tasks.
> This works fine for map tasks. However, for reduce tasks, jobs do not need reduce slots until the minimum number of map tasks have been completed.
> Here, we add checking whether reduce is ready to schedule (i.e. if a job has completed enough map tasks) when we increment number of users in a queue needing reduce slots.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira