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 "Hemanth Yamijala (JIRA)" <ji...@apache.org> on 2008/09/05 10:41:44 UTC
[jira] Commented: (HADOOP-4079) Check for invalid queues in
capacity scheduler
[ https://issues.apache.org/jira/browse/HADOOP-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628593#action_12628593 ]
Hemanth Yamijala commented on HADOOP-4079:
------------------------------------------
A simple proposal is to do what is done in HADOOP-3698. That is, we should parse the configuration at initialization and populate a mapping between queue names and the configured properties. This way, it will be easy to check if the map contains the queue name being requested in the APIs.
> 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.