[
https://issues.apache.org/jira/browse/MAPREDUCE-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756468#action_12756468
]
Hemanth Yamijala commented on MAPREDUCE-893:
--------------------------------------------
bq. Capacity-scheduler.xml still contains the default queue specific
properties. Shouldn't we remove them? If so, where shall the documentation of
scheduler properties be?
I think we should remove the properties that are no longer supposed to be
capacity-scheduler.xml and add a new file - something like
mapred-queues-for-cs.xml.template. This would only be for documentation
purposes and we could comment that users of capacity scheduler can rename this
to mapred-queues.xml adding more queues etc, based on the documentation
provided. Works ?
bq. Removed SchedulingDisplayInfo object all together and instead passing
QueueSchedulingContext to the QueueManager directly. Also, the corresponding
queueInfoMap completely. Is this change OK?
As discussed offline, I am not completely comfortable with this idea. I see the
QueueSchedulingContext as a core object of the CS, and wouldn't want the
framework to hold an instance of it (that too, in ways that are not very easily
detectable). I think the existing model of providing just a 'view' of the
scheduler state to the framework is better.
Regarding the rest of the questions, I am not really too strong on an opinion.
Let's try and minimize change to the extent possible at this stage in the
interest of caution. *smile*
> Provide an ability to refresh queue configuration without restart.
> ------------------------------------------------------------------
>
> Key: MAPREDUCE-893
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-893
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobtracker
> Reporter: Hemanth Yamijala
> Assignee: Vinod K V
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-893-20090915.1.txt,
> MAPREDUCE-893-20090917.2.txt
>
>
> While administering a cluster using multiple queues, administrators feel a
> need to refresh queue properties on the fly without needing to restart the
> JobTracker. This is partially supported for some properties such as queue
> ACLs (HADOOP-5396) and state (HADOOP-5913). The idea is to extend the
> facility to refresh other queue properties as well, including scheduler
> properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
