hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker
Date Mon, 16 Mar 2009 18:23:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682398#action_12682398

Doug Cutting commented on HADOOP-5396:

> One way to resolve this is by moving MRAdmin tool into the mapred package and deprecating
the current mapred.tools.MRAdmin. Thoughts?

Eventually we will restructure the mapred code into multiple packages, separating public APIs
(for which we'll generate javadoc) from internal APIs (for which we won't).  Once that's done,
we'll be able to have public classes which are not documented.

Do we yet have a Jira for this restructuring?  If that doesn't happen before this issue is
to be committed, then your workaround sounds reasonable.

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

View raw message