[
https://issues.apache.org/jira/browse/MAPREDUCE-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707183#comment-13707183
]
Ashwin Shankar commented on MAPREDUCE-5265:
-------------------------------------------
Thanks, I've incorporated all your comments except one mentioned below.
bq. RefreshUserMappingsProtocol.proto, GetUserMappingsPrototcol.proto, and the
supporting glue code is duplicated from HDFS – is there a way we can simply use
the HDFS version? I see the PB glue in HDFS is already marked LimitedPrivate
for HDFS and MapReduce, so it seems like we should just be using that rather
than duplicating it if possible.
I actually tried this when I started working on this JIRA,however I found that
I was not able to use HDFS classes in History server since the former is not
added as a dependency to the latter,which makes sense. Ideally we would want
move these protocol classes to common and then derive it in HDFS and History
server.
I'm planning to file a follow-up JIRA to do that. But for now,I felt that its
best to duplicate this part of the code.
> 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-10.txt, JHS_REFRESH-2.txt,
> JHS_REFRESH-4.txt, JHS_REFRESH-6.txt, JHS_REFRESH-8.txt, JHS_REFRESH-9.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
