[
https://issues.apache.org/jira/browse/HBASE-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197647#comment-13197647
]
Mubarak Seyed commented on HBASE-4991:
--------------------------------------
1. HBaseAdmin needs to have deleteRegion(byte[] encodedRegionName), which
invokes getMaster().deleteRegion(encodedRegionName)
(HMasterInterface will have deleteRegion(byte[] encodedRegionName))
2. HMaster needs to have deleteRegion(byte[] encodedRegionName).
* Do we need pre/post CP here?
* Need DeleteRegionHandler, need to check whether specified region belongs
to user regions (shouldn't be ROOT or META), turn off load balancer.
3. MasterDeleteRegionTracker (new class) will create deleteRegionNode (under
<zookeeper.znode.parent>/delete-region) and processing steps are almost like
MasterSchemaChangeTracker
4. DeleteRegionTracker (new class in RS side) will process
nodeChildrenChanged(), get the list of regions_to_be_deleted, check that those
regions are being hosted by the RS, if yes then
* doDeleteRegion
** call deleteRegion() in HRegionServer
*** disable the region split
*** close the region
*** remove from META
*** bridge the whole in META (extending the span of before or after
region)
*** remove region directory from HDFS
** update state in ZK
(<zookeeper.znode.parent>/delete-region/<encoded-region-name>)
5. MasterDeleteRegionTracker gets nodeDataChanged() Zk event, process the new
state and clean the znode (if region is deleted successfully) otherwise log the
debug message
I think i am missing some of the failure cases:
* update of before or after region
* Master fail-over
> Provide capability to delete named region
> -----------------------------------------
>
> Key: HBASE-4991
> URL: https://issues.apache.org/jira/browse/HBASE-4991
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
>
> See discussion titled 'Able to control routing to Solr shards or not' on
> lily-discuss
> User may want to quickly dispose of out of date records by deleting specific
> regions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
