[ https://issues.apache.org/jira/browse/HBASE-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924075#action_12924075 ]
Jean-Daniel Cryans commented on HBASE-3112: ------------------------------------------- While testing if HBASE-2522 was still there with the new master, I found out that we assign the parent regions when we re-enable the table (but disabling seems to work ok). > Enable and disable of table needs a bit of loving in new master > --------------------------------------------------------------- > > Key: HBASE-3112 > URL: https://issues.apache.org/jira/browse/HBASE-3112 > Project: HBase > Issue Type: Bug > Reporter: stack > Priority: Critical > Fix For: 0.90.0 > > > The tools are in place to do a more reliable enable/disable of tables. Some > work has been done to hack in a basic enable/disable but its not enough -- > see the test avro/thrift tests where a disable/enable/disable switchback can > confuse the table state (and has been disabled until this issue addressed). > This issue is about finishing off enable/disable in the new master. I think > we need to add to the table znode an enabling/disabling state rather than > have them binary with a watcher that will stop an enable (or disable) > starting until the previous completes (Currently we atomically switch the > state though the region close/open lags -- some work in enable/disable > handlers helps in that they won't complete till all regions have > transitioned.. but its not enough). > Need to add tests too. > Marking issue critical bug because loads of the questions we get on lists are > about enable/disable probs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.