[
https://issues.apache.org/jira/browse/HDFS-14447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855895#comment-16855895
]
Íñigo Goiri commented on HDFS-14447:
------------------------------------
Any thoughts on implementing {{GetUserMappingsProtocol}}?
The Namenode does:
{code}
@Override // GetUserMappingsProtocol
public String[] getGroupsForUser(String user) throws IOException {
if (LOG.isDebugEnabled()) {
LOG.debug("Getting groups for user " + user);
}
return UserGroupInformation.createRemoteUser(user).getGroupNames();
}
{code}
We could just do this or forward to each of the Namenodes and merge.
> RBF: Router should support RefreshUserMappingsProtocol
> ------------------------------------------------------
>
> Key: HDFS-14447
> URL: https://issues.apache.org/jira/browse/HDFS-14447
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: rbf
> Affects Versions: 3.1.0
> Reporter: Shen Yinjie
> Assignee: Shen Yinjie
> Priority: Major
> Fix For: HDFS-13891
>
> Attachments: HDFS-14447-HDFS-13891.01.patch,
> HDFS-14447-HDFS-13891.02.patch, HDFS-14447-HDFS-13891.03.patch,
> HDFS-14447-HDFS-13891.04.patch, HDFS-14447-HDFS-13891.05.patch,
> HDFS-14447-HDFS-13891.06.patch, HDFS-14447-HDFS-13891.07.patch,
> HDFS-14447-HDFS-13891.08.patch, HDFS-14447-HDFS-13891.09.patch, error.png
>
>
> HDFS with RBF
> We configure hadoop.proxyuser.xx.yy ,then execute hdfs dfsadmin
> -Dfs.defaultFS=hdfs://router-fed -refreshSuperUserGroupsConfiguration,
> it throws "Unknown protocol: ...RefreshUserMappingProtocol".
> RouterAdminServer should support RefreshUserMappingsProtocol , or a proxyuser
> client would be refused to impersonate.As shown in the screenshot
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
