You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Esteban Gutierrez (JIRA)" <ji...@apache.org> on 2017/03/07 21:49:38 UTC

[jira] [Commented] (HBASE-15941) HBCK repair should not unsplit healthy splitted region

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

Esteban Gutierrez commented on HBASE-15941:
-------------------------------------------

Hi [~syuanjiang], can you take a look to this approach? Basically if we are 100% sure that there is parent is present and the splits are valid daughters then we remove the parent and sideline the parent. Otherwise we fallback to the current approach. Thanks!


> HBCK repair should not unsplit healthy splitted region
> ------------------------------------------------------
>
>                 Key: HBASE-15941
>                 URL: https://issues.apache.org/jira/browse/HBASE-15941
>             Project: HBase
>          Issue Type: Improvement
>          Components: hbck
>    Affects Versions: 1.0.0
>            Reporter: Stephen Yuan Jiang
>            Assignee: Esteban Gutierrez
>         Attachments: HBASE-15941.master.001.patch
>
>
> Currently HBCK design in branch-1 has a flaw when repair option (the -fixHdfsOverlaps option specifically) is specified: it would wrongly merge split region (by looking at HDFS, it thinks that there exists overlapped regions - parent region and daughter regions covers the same key range, of course).  See HBASE-15940 for details.  
> This JIRA tracks the improvement not-to-merge split region in HBCK repair.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)