[
https://issues.apache.org/jira/browse/HADOOP-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680877#action_12680877
]
Hemanth Yamijala commented on HADOOP-5396:
------------------------------------------
bq. ... adding a seperate configuration file for queue acl's would increase
administrators burden to deal with one extra file for getting something done
Actually, in HADOOP-4348, there is
[feedback|https://issues.apache.org/jira/browse/HADOOP-4348?focusedCommentId=12638149&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12638149]
that indicates the other way round. A separate file is what is being viewed as
not only desirable, but necessary for managing these kinds of things.
Given that, I am +1 for Vinod's preference as well.
> 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.
