hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-3109) Support deletion of whole region
Date Sat, 19 Jul 2014 00:18:39 GMT

     [ https://issues.apache.org/jira/browse/HBASE-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Purtell resolved HBASE-3109.
-----------------------------------

    Resolution: Not a Problem

> Support deletion of whole region 
> ---------------------------------
>
>                 Key: HBASE-3109
>                 URL: https://issues.apache.org/jira/browse/HBASE-3109
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Jeff Zhang
>
> Like the bulk import, bulk deletion would also be useful and efficiency for users. The
following the instruction from stack:
> I think you could script it easy enough in TRUNK (I think you need
> TRUNK because you can ask it when a region is closed since there is no
> synchronous close of regions currently).
> 1. Close the region (See shell for how to send a close message or look
> at HBaseAdmin API doc).
> 2. While its closing, you may have to disable the region in .META.
> (See bin/*.rb scripts for how to mangle .META.).  This may not be
> necessary IIRC in TRUNK (In 0.20.x, it is necessary to prevent the
> region being opened elsewhere when the regionserver reports sucessful
> close).
> 3. Check the regionserver periodically for the closing region.  When
> its no longer mentioned in online regions, you know its closed.
> 4. Close the region that falls just after the one you just closed
> (Same trick w/ offlining above).  Do fixup on meta where you extend
> the key scope of this region so that it covers the region just closed
> by making its startkey that of the region just closed.
> 5. Reenable (in 0.20. this would mean flipping region to be enabled
> again -- in TRUNK, you might have to explicitly open it on a
> regionserver -- would have to check).



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

Mime
View raw message