[
https://issues.apache.org/jira/browse/HADOOP-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634050#action_12634050
]
Vinod K V commented on HADOOP-4178:
-----------------------------------
The patch submitted sets the default guaranteed capacity to be 100. This
doesn't seem to be right. For e.g, this won't let me get go running just by
creating two queues; the total capacity flows over 100 and the scheduler fails
to start.
Instead, we could knock this configuration off, take the default guaranteed
capacity of a queue to be -1. While starting off the scheduler, we iterate over
the list of queues. If the cumulative configured guaranteed-capacities go over
100, fail, otherwise distribute the remaining capacity (100 less cumulative
guaranteed-capacities) among the queues that are not configured. This way we
can kick -tart multiple queues just by creating them (i.e. simply via
mapred.queue.names).
The other three configuration parameters are useful in the current format.
> The capacity scheduler's defaults for queues should be configurable.
> --------------------------------------------------------------------
>
> Key: HADOOP-4178
> URL: https://issues.apache.org/jira/browse/HADOOP-4178
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/capacity-sched
> Affects Versions: 0.19.0
> Reporter: Owen O'Malley
> Assignee: Sreekanth Ramakrishnan
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: HADOOP-4178-1.patch, HADOOP-4178-2.patch
>
>
> The default values for the queue attributes should be configurable rather
> than hard coded.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
