You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Devaraj Das (JIRA)" <ji...@apache.org> on 2012/11/14 23:22:13 UTC

[jira] [Created] (HBASE-7161) Table does not come out of 'enabling' state

Devaraj Das created HBASE-7161:
----------------------------------

             Summary: Table does not come out of 'enabling' state
                 Key: HBASE-7161
                 URL: https://issues.apache.org/jira/browse/HBASE-7161
             Project: HBase
          Issue Type: Bug
    Affects Versions: 0.94.2
            Reporter: Devaraj Das


I was running a test, and the test failed because a table didn't get 'enabled' in the timeframe the test expected. When I checked the state of the table on ZK, it showed the state as 'enabling'. 

When I dug up the master logs, found that the BulkAssigner.bulkAssign returned false (the first line in the logs below), and the table never became 'enabled'. There was one region which could not be opened in the time bulkAssign ran (and that got 'opened' after the bulkAssign method returned). Also the table could not be enabled later on (from the hbase shell, for example), since the state of the table on ZK was 'enabling' (as opposed to 'disabled' and the table-state checks would fail).

{noformat}
2012-11-13 06:41:27,257 INFO org.apache.hadoop.hbase.master.handler.EnableTableHandler: Enabled table is done=false 
2012-11-13 06:41:49,569 DEBUG org.apache.hadoop.hbase.master.AssignmentManager: Handling transition=RS_ZK_REGION_OPENING, server=hrt20n32.foo.net,60020,1352782575357, region=0c0f9c71a81112f07c8f0ea130a65d05
2012-11-13 06:41:49,579 DEBUG org.apache.hadoop.hbase.master.AssignmentManager: Handling transition=RS_ZK_REGION_OPENING, server=hrt20n32.foo.net,60020,1352782575357, region=0c0f9c71a81112f07c8f0ea130a65d05
2012-11-13 06:41:49,586 DEBUG org.apache.hadoop.hbase.master.AssignmentManager: Handling transition=RS_ZK_REGION_OPENED, server=hrt20n32.foo.net,60020,1352782575357, region=0c0f9c71a81112f07c8f0ea130a65d05
2012-11-13 06:41:49,586 DEBUG org.apache.hadoop.hbase.master.handler.OpenedRegionHandler: Handling OPENED event for loadtest_d1,44444444,1352788441221.0c0f9c71a81112f07c8f0ea130a65d05. from hrt20n32.foo.net,60020,1352782575357; deleting unassigned node
2012-11-13 06:41:49,586 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign: master:60000-0x13af81eec6f0004 Deleting existing unassigned node for 0c0f9c71a81112f07c8f0ea130a65d05 that is in expected state RS_ZK_REGION_OPENED
2012-11-13 06:41:49,589 DEBUG org.apache.hadoop.hbase.master.AssignmentManager: The znode of region loadtest_d1,44444444,1352788441221.0c0f9c71a81112f07c8f0ea130a65d05. has been deleted.
2012-11-13 06:41:49,589 INFO org.apache.hadoop.hbase.master.AssignmentManager: The master has opened the region loadtest_d1,44444444,1352788441221.0c0f9c71a81112f07c8f0ea130a65d05. that was online on hrt20n32.foo.net,60020,1352782575357
{noformat}

The client (that invoked HBA.enableTable) gave up eventually (enableTable invokes isTableEnabled in a loop and in this case it was always returning false).

The handling on the master side for regions that take longer to get 'opened' can be improved.

--
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