hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "rahul k singh (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1105) CapacityScheduler: It should be possible to set queue hard-limit beyond it's actual capacity
Date Tue, 20 Oct 2009 09:02:01 GMT

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

rahul k singh updated MAPREDUCE-1105:

    Attachment: MAPREDUCE-1105-version20-2.patch

Implemented the all hemanth's comments except:

- checkMultipleAssignment is being called only when multiple assignment is set to true. So
we can verify for the exact number of tasks returned, i.e. tasks.size should never be more
than the expected number of tasks.

checkMultipleAssignment method takes mapAttempt and reduceAttempt as the string , and there
is a check for assignTask value to be null or empty and checking if any of the mapAttempt
or reduceAttempt being set.

Also there is a check to see if both mapAttempt and reduceAttempt are set and assignTask size
is 1.

> CapacityScheduler: It should be possible to set queue hard-limit beyond it's actual capacity
> --------------------------------------------------------------------------------------------
>                 Key: MAPREDUCE-1105
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1105
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: contrib/capacity-sched
>    Affects Versions: 0.21.0
>            Reporter: Arun C Murthy
>            Assignee: rahul k singh
>            Priority: Blocker
>             Fix For: 0.21.0
>         Attachments: MAPRED-1105-21-1.patch, MAPREDUCE-1105-version20-2.patch, MAPREDUCE-1105-version20.patch.txt
> Currently the CS caps a queue's capacity to it's actual capacity if a hard-limit is specified
to be greater than it's actual capacity. We should allow the queue to go upto the hard-limit
if specified.
> Also, I propose we change the hard-limit unit to be percentage rather than #slots.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message