You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2011/05/05 23:07:04 UTC
[jira] [Resolved] (HBASE-2736) Disable table does not work anymore
[ https://issues.apache.org/jira/browse/HBASE-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-2736.
--------------------------
Resolution: Cannot Reproduce
Resolving cannot reproduce. This seems to work now. This issue is also old.
> Disable table does not work anymore
> -----------------------------------
>
> Key: HBASE-2736
> URL: https://issues.apache.org/jira/browse/HBASE-2736
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.90.0
> Reporter: Andrei Dragomir
>
> When trying to disable a table, the shell exhausts the retries, then throws the following:
> {noformat}
> ERROR: org.apache.hadoop.hbase.RegionException: Retries exhausted, it took too long to wait for the table t1 to be disabled.
> {noformat}
> in HBaseAdmin.java:disableTable, after disabling, the code checks again, using isTableDisabled, which always returns false.
> Also, after running a disable, in Zookeeper, in "/hbase/UNASSIGNED", I get an entry, which is exactly the name of the only region of the table I am trying to disable. This leads me to believe this bug is somehow linked to HBASE-2694.
> This reproduces on my machine, our cluster, with freshly installed HBase, with new data, as well as with old one.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira