[
https://issues.apache.org/jira/browse/HBASE-9197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13737588#comment-13737588
]
stack commented on HBASE-9197:
------------------------------
A bunch of threads are blocked here in Master:
{code}
58255 NumberFormatException: "RpcServer.handler=0,port=57659" daemon prio=5
tid=7fa45524b000 nid=0x123ddb000 waiting for monitor entry [123dda000]
58256 java.lang.Thread.State: BLOCKED (on object monitor)
58257 ,...at
org.apache.hadoop.hbase.master.TableNamespaceManager.get(TableNamespaceManager.java:111)
58258 ,...- waiting to lock <78df23790> (a
org.apache.hadoop.hbase.master.TableNamespaceManager)
58259 ,...at
org.apache.hadoop.hbase.master.HMaster.getNamespaceDescriptor(HMaster.java:3070)
58260 ,...at
org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1773)
58261 ,...at
org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1814)
58262 ,...at
org.apache.hadoop.hbase.protobuf.generated.MasterAdminProtos$MasterAdminService$2.callBlockingMethod(MasterAdminProtos.java:26698)
58263 ,...at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2147)
58264 ,...at
org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1854)
{code}
I got some output and saw that we were shutting down in ns region in this test
because we were only avoiding meta (not system tables).
> TestAdmin#testShouldCloseTheRegionBasedOnTheEncodedRegionName shuts down the
> namespaces table and never starts it up again
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-9197
> URL: https://issues.apache.org/jira/browse/HBASE-9197
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Attachments: 9197.txt
>
>
> Because the ns table is offline, all subsequent tests just keep retrying and
> eventually fail (This contribs to the hung TestAdmin we've been seeing of
> late).
--
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
