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

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

comments :
CapacityTestUtils:

1.         ((FakeQueueManager) qm).getQueue(q.queueName).setProperties(p);
No need for casting qm is already FakeQueueManager.

TestQueueManagerRefresh
1.testRefreshFailureWithChangeOfHierarchy(JobQueueInfo[] queues => This 
parameter is not used.

QueueManager
1.Check if QueueRefresher parameter is null in refreshQueues method.


CapacityTaskScheduler.
1.Check for supportsPriority , it should not be updated as part of refresh.

2.JobInitializationPoller entries are part of capacity-scheduler.xml , but we 
are not refreshing capacity-scheduler.xml so we need to 
queue specific JobInitializationPoller entries to QueueSchedulingContext.


AbstractQueue
1.addChild method should be documented as being only used for testing.

Queue
1. there is no need for maintaining the fullyQualifiedName and name separatly . 
Instead we shuold always use fullyQualified name everywhere
and can provide method to get the normal queueName.

> 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.

Reply via email to