[
https://issues.apache.org/jira/browse/HADOOP-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681149#action_12681149
]
Sreekanth Ramakrishnan commented on HADOOP-5396:
------------------------------------------------
So, then by adding an extra file would mean that administrators would have to
deal with Queue ACL's in seperate file plus Service level acl's in another
file? Why don't we atleast merge these two together and use the same
configuration file {{hadoop-policy.xml}} for the queue related operations.
There is already refresh enabled to {{hadoop-policy.xml}}, so can we make use
of the same?
> 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
>
> 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.
