[
https://issues.apache.org/jira/browse/HADOOP-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreekanth Ramakrishnan updated HADOOP-5396:
-------------------------------------------
Attachment: hadoop-5396-2.patch
Attaching patch incorporating both Vinod's and Hemanths comments.
Following changes have been made to {{QueueManager}}:
* Changed {{initalize(Configuration)}} to {{initialize()}}
* Created a new method called {{refreshAcls()}} in {{QueueManager}} which only
refreshes queue acls.
Changed test cases to directly call QueueManager.refreshAcls instead of
starting MiniMRCluster
> Queue ACLs should be refreshed without requiring a restart of the job tracker
> -----------------------------------------------------------------------------
>
> Key: HADOOP-5396
> URL: https://issues.apache.org/jira/browse/HADOOP-5396
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Hemanth Yamijala
> Assignee: Vinod K V
> Attachments: cluster_setup.pdf, commands_manual.pdf,
> hadoop-5396-1.patch, hadoop-5396-2.patch, HADOOP-5396-3-svn.txt,
> HADOOP-5396-4-svn.txt
>
>
> In large shared deployments of the M/R clusters, it is normal that new users
> will periodically want to get access to some queues on the M/R framework.
> Requiring a JT restart for each such change is operationally inconvenient and
> seems an overkill. There should be a way for updating ACLs with new users
> without requiring a JT restart.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
