[jira] [Commented] (HBASE-22614) Master should provide the ability to delete a specified region

["stack (JIRA)" <ji...@apache.org>]

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

stack commented on HBASE-22614:
-------------------------------

[~Bo Cui] You say that if lots of overlapping regions, 'hbase shell is not available.' Is that the case? What do you see? (in hbase1 vs hbase2). Thanks.

If shell, you could just delete row in meta table?

Please say more on this... if it is hbase2:

bq. If there is a overlap in hbase, it can not be fixed completely with hbck, because there is old regioninfo in master regionStates.

In your scenario, is one of the regions correct or do both overlap in different ways and you want to delete both and create a new one to span the gap?



> Master should provide the ability to delete a specified region
> --------------------------------------------------------------
>
>                 Key: HBASE-22614
>                 URL: https://issues.apache.org/jira/browse/HBASE-22614
>             Project: HBase
>          Issue Type: Improvement
>          Components: hbck
>    Affects Versions: 1.3.1, 2.1.0
>            Reporter: Bo Cui
>            Priority: Major
>
> If there is a overlap in hbase, it can not be fixed completely with hbck, because there is old regioninfo in master regionStates.
> Key reproducible steps:
> 1.Constructing a overlap scenario（region1 and region2 have the same startKey,region1 is opend on the regionserver1,region2 is opend on the regionserver2）
> 2.use hbck repair
> 3.regionserver1 or regionserver2 aborted
> 4.region1 or region2 is reopened
>  
> Master should provide the ability to remove a specified region, and hbck uses the ability.
> {code:java}
> public deleteSpecifiedRegion(regionName){
> if(MetaTableAccessor.getRegionResult(regionName)==null){
> RegionStates.removeRegion(regionName)
> }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)