[
https://issues.apache.org/jira/browse/HBASE-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212228#comment-13212228
]
Todd Lipcon commented on HBASE-4991:
------------------------------------
I'm cool with the API now. I'm a bit nervous about the complexity of the
implementation - the fact that this (and the online schema change) have to do
things like disable splits and disable balancing is a little "smelly" to me.
But, I don't necessarily have a better idea.
In terms of testing before commit, I'd like to see a kind of stress test which
can be run continuously that does something like the following in a loop:
- create a table with 10 regions
- insert 10 rows into each region
- pick a random order to delete the regions
- start some threads which perform full table scans to count rows.
concurrently, delete each of the regions in the above random order
- number of rows should drop 100->90->80, etc.
- drop table
If we can run this test continuously, and the test can still succeed even if we
periodically kill the master or one of the RSes, it seems sufficient.
> 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
