[
https://issues.apache.org/jira/browse/HADOOP-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634480#action_12634480
]
Hemanth Yamijala commented on HADOOP-4079:
------------------------------------------
- The warning statement refers to hadoop-defaults, but the configuration can be
in hadoop-site as well. I would suggest we print something like: "Queue
<queue-name> is not configured in mapred.queue.names property in site
configuration."
- The test case {{testGetQueues}} must configure more than one queue and verify
they are present. The names should also be different from 'default'.
> 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
>
> Attachments: HADOOP-4079-1.patch
>
>
> 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.
