Enis Soztutar created HBASE-6469:
------------------------------------
Summary: Failure on enable/disable table will cause table state in
zk to be left as enabling/disabling until master is restart
Key: HBASE-6469
URL: https://issues.apache.org/jira/browse/HBASE-6469
Project: HBase
Issue Type: Bug
Affects Versions: 0.96.0, 0.94.2
Reporter: Enis Soztutar
Assignee: Enis Soztutar
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 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
