[
https://issues.apache.org/jira/browse/HBASE-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729423#action_12729423
]
Jonathan Gray commented on HBASE-1636:
--------------------------------------
As long as all these operations are asynchronous and rely on polling/intervals,
it's going to be clunky to deal with.
We aren't doing anything wacky when we disable like compacting or anything,
right?
We need a "fool-proof" method of determining that a table is fully disabled.
Perhaps we should build a list of the regions, disable the table, and then hold
until we verify each region is offlined.
Once properly disabled, should be able to quickly delete the table and all
corresponding rows in META.
> 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
>
> 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.
