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 "Hadoop QA (JIRA)" <ji...@apache.org> on 2012/06/29 22:55:43 UTC
[jira] [Commented] (MAPREDUCE-4385)
FairScheduler.maxTasksToAssign() should check for
fairscheduler.assignmultiple.maps < TaskTracker.availableSlots
[ https://issues.apache.org/jira/browse/MAPREDUCE-4385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404207#comment-13404207 ]
Hadoop QA commented on MAPREDUCE-4385:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12533888/MR-4385.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2534//console
This message is automatically generated.
> FairScheduler.maxTasksToAssign() should check for fairscheduler.assignmultiple.maps < TaskTracker.availableSlots
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4385
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4385
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 1.0.3
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Attachments: MR-4385.patch
>
>
> FairScheduler.maxTasksToAssign() can potentially return a value greater than the available slots. Currently, we rely on canAssignMaps()/canAssignReduces() to reject such requests.
> These additional calls can be avoided by check against the available slots in maxTasksToAssign().
--
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