[HBASE-3075] Reliable delete table

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Assignee: Unassigned
• Reporter: Michael Stack
• Created: 03/Oct/10 05:14
• Updated: 12/Jun/22 00:12
• Resolved: 16/Jul/14 23:07

Description

New master makes it so enable/disable show as near instantaneous but behind the scenes we still have to do the region close/opens. These can take time. HBASE-3063 adds into the disable table handler a wait on regions leaving regions in transition but, what if the user did enable/disable/enable/disable then delete. Turns out we don't do this well. It confuses. See the TestThriftServer where we've disabled such a sequence. This issue is about working on making delete work better; e.g. why bother closing stuff if we're going to delete it — just abort the tables regions and save all the flushing, etc., that slows the close-before-delete.

Issue Links

• is related to: HBASE-2522 Disabling a table during a split (tricky) can leave the daughter regions assigned and marked offline in .META.
• is related to: HBASE-2736 Disable table does not work anymore
• is related to: HBASE-2929 HBaseAdmin.disableTable() took too long to run