You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Sreekanth Ramakrishnan (JIRA)" <ji...@apache.org> on 2008/09/22 12:22:44 UTC

[jira] Commented: (HADOOP-4178) The capacity scheduler's defaults for queues should be configurable.

    [ https://issues.apache.org/jira/browse/HADOOP-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633202#action_12633202 ] 

Sreekanth Ramakrishnan commented on HADOOP-4178:
------------------------------------------------

According to [HADOOP-4079|https://issues.apache.org/jira/browse/HADOOP-4079] , checking for the invalid queues should be done at global level i.e. for the requisite parameter for specific job queues. The Capacity scheduler should only check for the parameters it requires to be present. If it is not present it should fall back to the defaults which is configured in this JIRA and use the same.  So, if required we can check for negative capacity and user limits here and consider them to be invalid. Assume that _QueueManager_ always gives us the right valid queues when _CapacityTaskScheduler_ is initialized.

> 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
>            Reporter: Owen O'Malley
>            Assignee: Sreekanth Ramakrishnan
>         Attachments: HADOOP-4178-1.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.