[ https://issues.apache.org/jira/browse/MAPREDUCE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744910#action_12744910 ]
rahul k singh commented on MAPREDUCE-861: ----------------------------------------- We had an offline discussion with owen and eric. There was an agreement in principal to use option 2 with slight modification . So all the configuration still remains the same except <schedulingContext> part. would change to <properties> Hence the new configuration would look like: {code:xml} <queue> <name>queue1</name> <properties> <property key="capacity" value="40" /> <property key="maxcapacity" value="50" /> </properties> <queue> <name>subQueue1</name> <acl-submit-job>alice,bob</acl-submit-job> <state>running</state> <properties> <property key="capacity" value="40" /> <property key="maxcapacity" value="50" /> </properties> </queue> </queue> {code} > 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.