[ 
https://issues.apache.org/jira/browse/HBASE-13326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378327#comment-14378327
 ] 

Matteo Bertozzi commented on HBASE-13326:
-----------------------------------------

you can try that from branch-1 and branch-1.0.
just follow the 4 steps. you can just use the start-hbase.sh/stop-hbase.sh with 
the standalone setup
{noformat}
2015-03-24 18:12:02,716 WARN  [MASTER_TABLE_OPERATIONS-u1410vm:33880-0] 
zookeeper.ZKTableStateManager: Moving table t state from ENABLING to ENABLING
2015-03-24 18:12:02,717 INFO  [MASTER_TABLE_OPERATIONS-u1410vm:33880-0] 
zookeeper.ZKTableStateManager: SET STATE IN ZK t newState=ENABLING
2015-03-24 18:12:02,724 INFO  [MASTER_TABLE_OPERATIONS-u1410vm:33880-0] 
handler.EnableTableHandler: Table 't' has 1 regions, of which 1 are offline.
2015-03-24 18:12:02,724 INFO  [MASTER_TABLE_OPERATIONS-u1410vm:33880-0] 
handler.EnableTableHandler: Bulk assigning 1 region(s) across 1 server(s), 
retainAssignment=true
2015-03-24 18:12:02,726 INFO  
[u1410vm,33880,1427220688982-GeneralBulkAssigner-0] master.AssignmentManager: 
Assigning 1 region(s) to u1410vm,41265,1427220690076
2015-03-24 18:12:02,730 INFO  
[u1410vm,33880,1427220688982-GeneralBulkAssigner-0] master.AssignmentManager: 
Updating the state to OFFLINE to allow to be reassigned by SSH
2015-03-24 18:12:02,730 INFO  
[u1410vm,33880,1427220688982-GeneralBulkAssigner-0] master.AssignmentManager: 
Skip assigning t,,1427220651002.7285f3f1efc8358c2b79d165cc4bd4e6., it is on a 
dead but not processed yet server: u1410vm,53436,1427220586432
2015-03-24 18:12:02,731 INFO  
[u1410vm,33880,1427220688982-GeneralBulkAssigner-0] master.AssignmentManager: 
failed to force region state to offline or failed to set it offline in ZK, will 
reassign later: {ENCODED => 7285f3f1efc8358c2b79d165cc4bd4e6, NAME => 
't,,1427220651002.7285f3f1efc8358c2b79d165cc4bd4e6.', STARTKEY => '', ENDKEY => 
''}
2015-03-24 18:12:02,736 INFO  [AM.-pool1-t1] master.AssignmentManager: Skip 
assigning t,,1427220651002.7285f3f1efc8358c2b79d165cc4bd4e6., it is on a dead 
but not processed yet server: u1410vm,53436,1427220586432
{noformat}

> Disabled table can't be enabled after HBase is restarted
> --------------------------------------------------------
>
>                 Key: HBASE-13326
>                 URL: https://issues.apache.org/jira/browse/HBASE-13326
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.0.0, 1.1.0
>            Reporter: Dima Spivak
>            Assignee: Matteo Bertozzi
>            Priority: Blocker
>
> The folks at Intel discovered a pretty nasty bug in 1.0 and 1.1 (but not 
> master). Steps to reproduce:
> 1. Create a table, any table.
> 2. Disable the table.
> 3. Restart HBase.
> 4. Try enabling the table.
> The table won't become enabled and the master web UI will indicate a 
> never-ending region in transition. Also worth noting is that [~mbertozzi] dug 
> in and noted that this isn't happening in the master branch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to