hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5396) Queue ACLs should be refreshed without requiring a restart of the job tracker
Date Tue, 31 Mar 2009 10:21:50 GMT

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

Vinod K V commented on HADOOP-5396:

bq. 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.
Talked to Arun offline and he is also of the same opinioin. In which case, I would let MRAdmin
be in the tools sub-package as it is now and have AdminOperationsProtocol as a public interface
with a javadoc warning saying that it is not to be used by users directly and that it is prone
to changes.

> 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