hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei-Chiu Chuang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-13723) Occasional "Should be different group" error in TestRefreshUserMappings#testGroupMappingRefresh
Date Wed, 11 Jul 2018 17:05:00 GMT

     [ https://issues.apache.org/jira/browse/HDFS-13723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Wei-Chiu Chuang updated HDFS-13723:
-----------------------------------
    Fix Version/s: 3.0.4
                   3.1.1

> Occasional "Should be different group" error in TestRefreshUserMappings#testGroupMappingRefresh
> -----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-13723
>                 URL: https://issues.apache.org/jira/browse/HDFS-13723
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: security, test
>    Affects Versions: 3.0.0
>            Reporter: Siyao Meng
>            Assignee: Siyao Meng
>            Priority: Major
>             Fix For: 3.2.0, 3.1.1, 3.0.4
>
>         Attachments: HDFS-13723.001.patch, HDFS-13723.002.patch, HDFS-13723.003.patch
>
>
> In some occasions, the user-group mapping refresh timeout test assertion would fail due
to the mapping didn't refresh in time, reporting "Should be different group".
>  
> Trace:
> {code:java}
> java.lang.AssertionError: Should be different group 
> at org.apache.hadoop.security.TestRefreshUserMappings.testGroupMappingRefresh(TestRefreshUserMappings.java:153)
> :
> :
> 2018-07-04 19:35:21,073 [BP-1412052829-172.26.17.254-1530758120647 heartbeating to localhost/127.0.0.1:39524] INFO
datanode.DataNode (BPOfferService.java:processCommandFromActive(759)) - Got finalize command
for block pool BP-1412052829-172.26.17.254-1530758120647
> Getting groups in MockUnixGroupsMapping
> 2018-07-04 19:35:21,090 [IPC Server handler 6 on 39524] INFO FSNamesystem.audit (FSNamesystem.java:logAuditMessage(7805))
- allowed=true	ugi=jenkins (auth:SIMPLE)	ip=/127.0.0.1 cmd=datanodeReport	src=null	dst=null
perm=null	proto=rpc
> 2018-07-04 19:35:21,092 [main] INFO hdfs.MiniDFSCluster (MiniDFSCluster.java:waitActive(2629))
- Cluster is active
> 2018-07-04 19:35:21,095 [IPC Server handler 7 on 39524] INFO FSNamesystem.audit (FSNamesystem.java:logAuditMessage(7805))
- allowed=true	ugi=jenkins (auth:SIMPLE)	ip=/127.0.0.1 cmd=datanodeReport	src=null	dst=null
perm=null	proto=rpc
> 2018-07-04 19:35:21,096 [main] INFO hdfs.MiniDFSCluster (MiniDFSCluster.java:waitActive(2629))
- Cluster is active
> first attempt:
> [jenkins11, jenkins12]
> second attempt, should be same:
> [jenkins11, jenkins12]
> 2018-07-04 19:35:21,101 [IPC Server handler 5 on 39524] INFO namenode.NameNode (NameNodeRpcServer.java:refreshUserToGroupsMappings(1648))
- Refreshing all user-to-groups mappings. Requested by user: jenkins
> 2018-07-04 19:35:21,101 [IPC Server handler 5 on 39524] INFO security.Groups (Groups.java:refresh(401))
- clearing userToGroupsMap cache
> Refreshing groups in MockUnixGroupsMapping
> 2018-07-04 19:35:21,102 [IPC Server handler 5 on 39524] INFO FSNamesystem.audit (FSNamesystem.java:logAuditMessage(7805))
- allowed=true	ugi=jenkins (auth:SIMPLE)	ip=/127.0.0.1 cmd=refreshUserToGroupsMappings	src=null
dst=null	perm=null	proto=rpc
> Refresh user to groups mapping successful
> third attempt(after refresh command), should be different:
> Getting groups in MockUnixGroupsMapping
> [jenkins21, jenkins22]
> fourth attempt(after timeout), should be different:
> [jenkins21, jenkins22]
> Getting groups in MockUnixGroupsMapping
> 2018-07-04 19:35:22,204 [main] INFO hdfs.MiniDFSCluster (MiniDFSCluster.java:shutdown(1965))
- Shutting down the Mini HDFS Cluster
> {code}
>  
> Solution:
> Increase the timeout slightly, and place debugging message in load() and reload() methods
in class GroupCacheLoader.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message