[
https://issues.apache.org/jira/browse/HBASE-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219805#comment-13219805
]
stack commented on HBASE-4991:
------------------------------
bq. Well, client's deleteRegion call is asynchronous so no fail-over if client
has to do the business.
Fair enough. I was suggesting doing it as a client script because then it'd be
outside of the servers and easier to test. If client dies, restart it, it
looks in zk for work to do and carries on from where the last client was. But
no biggie.
What about my question about why we delegate merge/delete out to the
regionservers? Why not have them do nothing but the close and then have the
master do the remove or merging of fs content and fixup in meta? Would that be
less moving parts?
Let me give some higher level feedback in a sec.
@Jieshan Yes that'll work. How you do it? You have a patch?
> 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
> Assignee: Mubarak Seyed
> Fix For: 0.94.0
>
> Attachments: HBASE-4991.trunk.v1.patch, HBASE-4991.trunk.v2.patch
>
>
> 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
