hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-3075) Reliable delete table
Date Wed, 16 Jul 2014 23:09:05 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064301#comment-14064301
] 

Andrew Purtell edited comment on HBASE-3075 at 7/16/14 11:07 PM:
-----------------------------------------------------------------

There have been a number of improvements since this issue was filed. Please reopen or file
a new JIRA detailing remaining issues with current code if we should actively pursue this.


was (Author: apurtell):
There have been a number of improvements since this issue was filed. Please reopen or file
a new JIRA detailing remaining issues with current code.

> Reliable delete table
> ---------------------
>
>                 Key: HBASE-3075
>                 URL: https://issues.apache.org/jira/browse/HBASE-3075
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message