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

Hemanth Yamijala commented on HADOOP-4079:
------------------------------------------

Considering how the code has turned out, the Capacity Scheduler iterates over 
queues it gets from the framework's {{QueueManager}} class. Now, when it asks 
the {{CapacitySchedulerConf}} for a property for this queue, if nothing is 
configured for this queue in {{capacity-scheduler.xml}}, a hard-coded default 
value is returned. This may not be what the administrator intended, because the 
defaults are not defined by him/her. Hence, this issue exists.

HADOOP-4178 is trying to implement a mechanism to make these default values 
itself configurable. If it does that, then it would be a feature that if a 
property is not configured for a queue in the capacity scheduler's 
configuration, the configured default is used. This makes it very simple for 
the administrator to define new queues. And it would invalidate the need to 
check for invalid queues, as required by this issue.

So in summary, if HADOOP-4178 is fixed, we can mark this bug as invalid. 
Comments ?

> Check for invalid queues in capacity scheduler
> ----------------------------------------------
>
>                 Key: HADOOP-4079
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4079
>             Project: Hadoop Core
>          Issue Type: Bug
>    Affects Versions: 0.19.0
>            Reporter: Hemanth Yamijala
>            Assignee: Hemanth Yamijala
>            Priority: Blocker
>             Fix For: 0.19.0
>
>
> The {{ResourceManagerConf}} class that is being moved to the capacity 
> scheduler of HADOOP-3445 needs to check for a queue name that is not 
> configured in the {{resource-manager-conf.xml}} file in its APIs and fail if 
> it is not available. This feature was originally available, but due to 
> subsequent changes in HADOOP-3698, queues are no longer being configured as 
> part of the mentioned configuration file. Hence we need a different mechanism 
> to check for valid queues.

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

Reply via email to