[HBASE-1636] disable and drop of table is flakey still

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.20.3, 0.90.0
• Assignee: Jean-Daniel Cryans
• Reporter: Michael Stack
• Created: 09/Jul/09 20:57
• Updated: 12/Oct/12 06:14
• Resolved: 04/Jan/10 19:11

Description

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:

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

This flakey disable/enable/drop is frustrating users. Need to fix.

Issue Links

• is blocked by: HBASE-1730 Near-instantaneous online schema and table state updates