Unable to stop a master that's waiting on -ROOT- during initialization
----------------------------------------------------------------------

                 Key: HBASE-5594
                 URL: https://issues.apache.org/jira/browse/HBASE-5594
             Project: HBase
          Issue Type: Bug
    Affects Versions: 0.92.1
            Reporter: Jean-Daniel Cryans
             Fix For: 0.92.2, 0.94.0, 0.96.0


We just had a case where the master (that was just restarted) was having a hard 
time assigning -ROOT- (all the PRI handlers were full already) so we tried to 
shutdown the cluster and even though all the RS closed down properly the master 
kept running being blocked on:

{noformat}
"master-sv4r20s12,10302,1331916142866" prio=10 tid=0x00007f3708008800 
nid=0x4b20 in Object.wait() [0x00007f370d1d0000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00000006030be3f8> (a 
org.apache.hadoop.hbase.zookeeper.RootRegionTracker)
        at java.lang.Object.wait(Object.java:485)
        at 
org.apache.hadoop.hbase.zookeeper.ZooKeeperNodeTracker.blockUntilAvailable(ZooKeeperNodeTracker.java:131)
        - locked <0x00000006030be3f8> (a 
org.apache.hadoop.hbase.zookeeper.RootRegionTracker)
        at 
org.apache.hadoop.hbase.zookeeper.ZooKeeperNodeTracker.blockUntilAvailable(ZooKeeperNodeTracker.java:104)
        - locked <0x00000006030be3f8> (a 
org.apache.hadoop.hbase.zookeeper.RootRegionTracker)
        at 
org.apache.hadoop.hbase.catalog.CatalogTracker.waitForRoot(CatalogTracker.java:313)
        at 
org.apache.hadoop.hbase.master.HMaster.assignRootAndMeta(HMaster.java:571)
        at 
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:501)
        at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:336)
        at java.lang.Thread.run(Thread.java:662)
{noformat}

I haven't checked the 0.90 code, we got this on 0.92.1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to