[
https://issues.apache.org/jira/browse/HADOOP-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680844#action_12680844
]
Sreekanth Ramakrishnan commented on HADOOP-5396:
------------------------------------------------
I think there was a discussion related to this issue for schedulers to be
allowed to re-read the configuration it was discussed on
[HADOOP-4522|https://issues.apache.org/jira/browse/HADOOP-5396], there is a
patch also out there which actually implements the mradmin which refreshes the
configuration. We should take a look at that.
In my opinion,adding a seperate configuration file for queue acl's would
increase administrators burden to deal with one extra file for getting
something done, we should avoid it if required.. Best way should be to add
{{Configuration.reload(String key)}} that way we can re-read the conf file and
then add/update the appropriate key.
> 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.
