[ https://issues.apache.org/jira/browse/HDFS-14545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880228#comment-17880228 ]
chuanjie.duan commented on HDFS-14545: -------------------------------------- RouterUserProtocol.java public void refreshSuperUserGroupsConfiguration() throws IOException { *_LOG_*.debug("Refresh superuser groups configuration in Router."); rpcServer.checkOperation({_}OperationCategory{_}.*_UNCHECKED_*); Set<FederationNamespaceInfo> nss = namenodeResolver.getNamespaces(); if (nss.isEmpty()) { ProxyUsers.{_}refreshSuperUserGroupsConfiguration{_}(); } else { RemoteMethod method = new RemoteMethod(RefreshUserMappingsProtocol.class, "refreshSuperUserGroupsConfiguration"); rpcClient.invokeConcurrent(nss, method); {color:#FF0000}ProxyUsers{color}{color:#FF0000}.{_}refreshSuperUserGroupsConfiguration{_}();{color} } } [~elgoiri] [~ayushtkn] , I would like to add a red line here, because after executing "hdfs dfsadmin -Dfs.defaultFS=hdfs://router-fed -refreshSuperUserGroupsConfiguration", although the backend Namenode has updated the ProxyUsers, the Router still prompts that it cannot proxy. This is confusing and hard to understand. Although the Router's ProxyUsers can be refreshed through the "hdfs dfsrouteradmin -refreshSuperUserGroupsConfiguration" method from HDFS-14983, it still requires two steps. In addition, the nss empty scenario is also troubling. If the Router is not listening to the Namenode, then what's the use of proxying? > RBF: Router should support GetUserMappingsProtocol > -------------------------------------------------- > > Key: HDFS-14545 > URL: https://issues.apache.org/jira/browse/HDFS-14545 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Íñigo Goiri > Assignee: Ayush Saxena > Priority: Major > Fix For: 3.3.0, HDFS-13891 > > Attachments: HDFS-14545-HDFS-13891-01.patch, > HDFS-14545-HDFS-13891-02.patch, HDFS-14545-HDFS-13891-03.patch, > HDFS-14545-HDFS-13891-04.patch, HDFS-14545-HDFS-13891-05.patch, > HDFS-14545-HDFS-13891-06.patch, HDFS-14545-HDFS-13891-07.patch, > HDFS-14545-HDFS-13891-08.patch, HDFS-14545-HDFS-13891-09.patch, > HDFS-14545-HDFS-13891-10.patch, HDFS-14545-HDFS-13891.000.patch > > > We should be able to check the groups for a user from a Router. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org