Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Tue, 18 Jun 2013 18:00:23 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12648918.1369239030403.133936.1371578423566@arcas>
In-Reply-To: <JIRA.12648918.1369239030403@arcas>
References: <JIRA.12648918.1369239030403@arcas>
Subject: [jira] [Commented] (MAPREDUCE-5265) Need an admin interface on
 history server with the ability to refresh super user groups,refresh user
 to group mappings,refresh admin acls,get groups given a username.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687014#comment-13687014 ] 

Jason Lowe commented on MAPREDUCE-5265:
---------------------------------------

Ah yes, sorry I missed that point.  That makes me lean even more towards implementing this via Hadoop Common RPC and straight protobufs (like what was done for the namenode equivalent to this feature) than the YARN route.  If for some reason we do stay with the YARN RPC, we'll need to put some MapReduce-specific prefix to the classes (e.g.: HistoryServerProtos becomes MRHistoryServerProtos) to avoid collisions with protocol messages for the upcoming, generic YARN history server.
                
> Need an admin interface on history server with the ability to refresh super user groups,refresh user to group mappings,refresh admin acls,get groups given a username.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5265
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5265
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: jobhistoryserver
>    Affects Versions: 2.1.0-beta
>            Reporter: Jason Lowe
>            Assignee: Ashwin Shankar
>         Attachments: JHS_REFRESH-2.txt, JHS_REFRESH-4.txt, JHS_REFRESH-6.txt
>
>
> The history server needs an admin interface with the ability to
> 1. refresh the super user groups configurations,
> 2. refresh user to group mappings,
> 3. refresh its admin acls,
> 4. get groups given a username 
> without requiring a restart of the history server.  This is analogous to the  -refreshSuperUserGroupsConfiguration capabilities provided by hdfs dfsadmin and yarn rmadmin. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira