[
https://issues.apache.org/jira/browse/HADOOP-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633623#action_12633623
]
Owen O'Malley commented on HADOOP-4079:
---------------------------------------
I'd suggest that we warn in the JobTracker log at start up if the capacity
scheduler configuration defines a queue that isn't present in the QueueManager.
It will most likely be a typo on one side or the other. Not defining properties
should be ok, since they will just fall back to the defaults defined via
HADOOP-4178.
> 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
> Components: contrib/capacity-sched
> 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.
