[
https://issues.apache.org/jira/browse/HADOOP-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697407#action_12697407
]
Vinod K V commented on HADOOP-5396:
-----------------------------------
Some comments:
- I think QueueManager.refresh(Configuration conf) should be deprecated in
favour of QueueManager.refresh() which should be added in this patch.
- bq. Should the API be refreshQueueAcls() ?
The command should be -refreshQueueAcls instead of -refreshQueueAcl in the
same vein. Also, the command summary in MRAdmin.java should read
"-refreshQueueAcls: Reload the queue acls\n\t\tJobTracker will reload the
*mapred-queue-acls file*.\n";
> 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-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.
