[
https://issues.apache.org/jira/browse/MAPREDUCE-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071465#comment-13071465
]
Hadoop QA commented on MAPREDUCE-2729:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12487910/MAPREDUCE-2729.patch
against trunk revision 1150926.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/504//console
This message is automatically generated.
> 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
