[ https://issues.apache.org/jira/browse/HBASE-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753144#comment-13753144 ]
Hadoop QA commented on HBASE-9321: ---------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12600506/trunk-9321_v3.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 12 new or modified tests. {color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop 1.0 profile. {color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 lineLengths{color}. The patch does not introduce lines longer than 100 {color:red}-1 site{color}. The patch appears to cause mvn site goal to fail. {color:red}-1 core tests{color}. The patch failed these unit tests: org.apache.hadoop.hbase.rest.TestScannerResource Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/6961//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6961//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6961//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6961//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6961//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6961//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6961//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6961//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6961//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/6961//console This message is automatically generated. > Contention getting the current user in RpcClient$Connection.writeRequest > ------------------------------------------------------------------------ > > Key: HBASE-9321 > URL: https://issues.apache.org/jira/browse/HBASE-9321 > Project: HBase > Issue Type: Bug > Affects Versions: 0.95.2 > Reporter: Jean-Daniel Cryans > Assignee: Jimmy Xiang > Priority: Critical > Fix For: 0.98.0, 0.96.0 > > Attachments: trunk-9321.patch, trunk-9321_v2.patch, > trunk-9321_v3.patch > > > I've been running tests on clusters with "lots" of regions, about 400, and > I'm seeing weird contention in the client. > This one I see a lot, hundreds and sometimes thousands of threads are blocked > like this: > {noformat} > "htable-pool4-t74" daemon prio=10 tid=0x00007f2254114000 nid=0x2a99 waiting > for monitor entry [0x00007f21f9e94000] > java.lang.Thread.State: BLOCKED (on object monitor) > at > org.apache.hadoop.security.UserGroupInformation.getCurrentUser(UserGroupInformation.java:466) > - waiting to lock <0x00000000fb5ad000> (a java.lang.Class for > org.apache.hadoop.security.UserGroupInformation) > at > org.apache.hadoop.hbase.ipc.RpcClient$Connection.writeRequest(RpcClient.java:1013) > at org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1407) > at > org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1634) > at > org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1691) > at > org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.multi(ClientProtos.java:27339) > at > org.apache.hadoop.hbase.client.MultiServerCallable.call(MultiServerCallable.java:105) > at > org.apache.hadoop.hbase.client.MultiServerCallable.call(MultiServerCallable.java:43) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:183) > {noformat} > While the holder is doing this: > {noformat} > "htable-pool17-t55" daemon prio=10 tid=0x00007f2244408000 nid=0x2a98 runnable > [0x00007f21f9f95000] > java.lang.Thread.State: RUNNABLE > at java.security.AccessController.getStackAccessControlContext(Native > Method) > at java.security.AccessController.getContext(AccessController.java:487) > at > org.apache.hadoop.security.UserGroupInformation.getCurrentUser(UserGroupInformation.java:466) > - locked <0x00000000fb5ad000> (a java.lang.Class for > org.apache.hadoop.security.UserGroupInformation) > at > org.apache.hadoop.hbase.ipc.RpcClient$Connection.writeRequest(RpcClient.java:1013) > at org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1407) > at > org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1634) > at > org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1691) > at > org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.multi(ClientProtos.java:27339) > at > org.apache.hadoop.hbase.client.MultiServerCallable.call(MultiServerCallable.java:105) > at > org.apache.hadoop.hbase.client.MultiServerCallable.call(MultiServerCallable.java:43) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:183) > {noformat} -- 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