You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2014/09/15 22:07:37 UTC
[jira] [Resolved] (HBASE-6469) Failure on enable/disable table will
cause table state in zk to be left as enabling/disabling until master is
restarted
[ https://issues.apache.org/jira/browse/HBASE-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-6469.
--------------------------
Resolution: Invalid
Resolving as no longer valid. Master branch is 'different' now -- no zk -- and branch-1 will likely get same change. Reopen if fix for 0.94-0.98.
> Failure on enable/disable table will cause table state in zk to be left as enabling/disabling until master is restarted
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-6469
> URL: https://issues.apache.org/jira/browse/HBASE-6469
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.94.6
> Reporter: Enis Soztutar
> Assignee: rajeshbabu
> Priority: Critical
> Attachments: 6469-expose-force-r3.patch, HBASE-6469.patch, HBASE-6469_2.patch, HBASE-6469_3.patch, HBASE-6469_4.patch, HBASE-6469_retry_enable_or_disable.patch
>
>
> In Enable/DisableTableHandler code, if something goes wrong in handling, the table state in zk is left as ENABLING / DISABLING. After that we cannot force any more action from the API or CLI, and the only recovery path is restarting the master.
> {code}
> if (done) {
> // Flip the table to enabled.
> this.assignmentManager.getZKTable().setEnabledTable(
> this.tableNameStr);
> LOG.info("Table '" + this.tableNameStr
> + "' was successfully enabled. Status: done=" + done);
> } else {
> LOG.warn("Table '" + this.tableNameStr
> + "' wasn't successfully enabled. Status: done=" + done);
> }
> {code}
> Here, if done is false, the table state is not changed. There is also no way to set skipTableStateCheck from cli / api.
> We have run into this issue a couple of times before.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)