You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2010/01/04 20:11:58 UTC
[jira] Resolved: (HBASE-1636) disable and drop of table is flakey
still
[ https://issues.apache.org/jira/browse/HBASE-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Daniel Cryans resolved HBASE-1636.
---------------------------------------
Resolution: Fixed
Closing the issue, I didn't see any problem using this fixes enclosed in the sub-tasks.
> disable and drop of table is flakey still
> -----------------------------------------
>
> Key: HBASE-1636
> URL: https://issues.apache.org/jira/browse/HBASE-1636
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: Jean-Daniel Cryans
> Fix For: 0.20.3, 0.21.0
>
> Attachments: hbase-hbase-master-ip-10-212-65-235.log, hbase-hbase-regionserver-ip-10-212-66-112.log
>
>
> Just now, cheddar up on IRC had table of 2k regions. A disable and drop gave him 2k rows in meta of historian info. He couldn't progress. Had to make below script for him:
> {code}
> meta = HTable.new(".META.")
> historian = "historian:"
> scanner = meta.getScanner([historian].to_java(java.lang.String))
> while (result = scanner.next())
> meta.deleteAll(result.getRow())
> end
> exit 0
> {code}
> This flakey disable/enable/drop is frustrating users. Need to fix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.