[
https://issues.apache.org/jira/browse/HADOOP-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694378#action_12694378
]
Sreekanth Ramakrishnan commented on HADOOP-5396:
------------------------------------------------
Took a look at the patch, everything looks fine, except few minor issues,
listed down below:
* Remove mapred-queues.xml, should be generated when you do build. Remove it
from patch.
* Is the mapred-queues.xml really required to be default resource in JobConf?
The QueueManager is the one which requires the list of queues and acls related
to it. Reloading of the same is done by AdminProtocol. So this resource ideally
should be removed from JobConf.
* Should we define the queue config resource file name in JobTracker? Can we
move it to QueueManager? i.e. we can just change
{{QueueManager.initalize(conf)}} to add the queue resource file there and
continue?
Minor Nit:
* There is "\ No newline at end of file" in the file MRAdmin
> 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: 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.
