You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2020/09/08 19:05:00 UTC

[jira] [Resolved] (HBASE-24995) MetaFixer fails to fix overlaps when multiple tables have overlaps

     [ https://issues.apache.org/jira/browse/HBASE-24995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Stack resolved HBASE-24995.
-----------------------------------
    Fix Version/s: 2.3.2
                   2.4.0
                   3.0.0-alpha-1
     Hadoop Flags: Reviewed
       Resolution: Fixed

Pushed to branch-2.3+ (wouldn't go back to branch-2.2 as is). Thanks for digging in here [~arshad.mohammad]

 

> MetaFixer fails to fix overlaps when multiple tables have overlaps
> ------------------------------------------------------------------
>
>                 Key: HBASE-24995
>                 URL: https://issues.apache.org/jira/browse/HBASE-24995
>             Project: HBase
>          Issue Type: Bug
>          Components: hbck2
>    Affects Versions: 3.0.0-alpha-1, 2.2.3
>            Reporter: Mohammad Arshad
>            Assignee: Mohammad Arshad
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.4.0, 2.3.2
>
>
> MetaFixer fails to fix overlaps when multiple tables have overlaps
> *Steps to reproduce from UT.*
> # Create table t1 and t2 with split keys, ["bbb", "ccc", "ddd", "eee"]
> # Create extra region in both t1 and t2 with start key "bbb" and end key "ddd"
> # Run catalog janitor, It will report total 4 overlaps, 2 from each table.
> # Run MetaFixer, wait for merges to finish.
> # Run the catalog janitor again and verify report, there should not be any overlap
> # Overlap still exists. Reproduced!!!
> *Analysis.*
> * When I run the same scenario for just one table t1, overlaps are fixed successfully.
> * Seems problem with MetaFixer#calculateMerges. 
> * I think merges should be calculated within a table. Across the table merge does not have significance.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)