hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "rahul k singh (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-861) Modify queue configuration format and parsing to support a hierarchy of queues.
Date Mon, 24 Aug 2009 08:30:59 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746763#action_12746763
] 

rahul k singh commented on MAPREDUCE-861:
-----------------------------------------

small correction above:
getLeafQueues is actually getLeafQueueNames().

Some more clarification in terms of names of queue:

1 . The name of the queues would be <parent>.<child>.<grandChild>. 
for example:
{code:xml}
<queue>
   <name>q</name>
    <queue>
        <name>p</name>
    </queue>
 </queue>
{code}

In the above example : There are 2 queues. "q" is a root level queue and "p" is a child of
"q".
The name of queue "q" would be "q";
The name of queue "p" would be "q.p". 
We would always use this completely qualified name in the implementation.

Users cannot name a queue like <queue-name>.<queue-name> as "." is used as separator.







> Modify queue configuration format and parsing to support a hierarchy of queues.
> -------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-861
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-861
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>            Reporter: Hemanth Yamijala
>            Assignee: rahul k singh
>
> MAPREDUCE-853 proposes to introduce a hierarchy of queues into the Map/Reduce framework.
This JIRA is for defining changes to the configuration related to queues. 
> The current format for defining a queue and its properties is as follows: mapred.queue.<queue-name>.<property-name>.
For e.g. mapred.queue.<queue-name>.acl-submit-job. The reason for using this verbose
format was to be able to reuse the Configuration parser in Hadoop. However, administrators
currently using the queue configuration have already indicated a very strong desire for a
more manageable format. Since, this becomes more unwieldy with hierarchical queues, the time
may be good to introduce a new format for representing queue configuration.

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


Mime
View raw message