[
https://issues.apache.org/jira/browse/MAPREDUCE-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675358#comment-13675358
]
Hadoop QA commented on MAPREDUCE-5265:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12586211/JHS_REFRESH-2.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3730//console
This message is automatically generated.
> 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
>
>
> 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
