[ 
https://issues.apache.org/jira/browse/HADOOP-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod K V updated HADOOP-5396:
------------------------------

    Attachment: HADOOP-5396-3-svn.txt

Attaching patch incorporating the above.
 - Also deprecated o.a.h.m.tools.MRAdmin in favour of o.a.h.m.MRAdmin.

`ant test-patch` gave
{code}
     [exec] -1 overall.
     [exec]
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]
     [exec]     +1 tests included.  The patch appears to include 7 new or 
modified tests.
     [exec]
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning 
messages.
     [exec]
     [exec]     +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
     [exec]
     [exec]     -1 findbugs.  The patch appears to introduce 1 new Findbugs 
warnings.
     [exec]
     [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath 
integrity.
     [exec]
     [exec]     -1 release audit.  The applied patch generated 653 release 
audit warnings (more than the trunk's current 652 warnings).
{code}

The release audit warning is for the newly added conf/mapred-queues.xml. The 
FindBugs warning ??"The class name org.apache.hadoop.mapred.tools.MRAdmin 
shadows the simple name of the superclass org.apache.hadoop.mapred.MRAdmin"?? 
is regarding the deprecated MRAdmin class.

> 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
>
>
> 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.

Reply via email to