You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Mohammad Arshad (Jira)" <ji...@apache.org> on 2020/08/24 04:14:00 UTC
[jira] [Commented] (HBASE-24916) Region hole contains wrong regions
pair when hole is created by first region deletion
[ https://issues.apache.org/jira/browse/HBASE-24916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182939#comment-17182939 ]
Mohammad Arshad commented on HBASE-24916:
-----------------------------------------
I think hole was created directly by deleting the region from meta. Hole was not created by any problematic hbck2 command.
When a region hole is created by deleting last region of a table then hole has the region pair as <second last region, RegionInfo#UNDEFINED>
But when a region hole is created by deleting the first region then hole has the region pair as <previous tables' last region , second region>.
This seems wrong. This hole region pair should be <RegionInfo#UNDEFINED, second region>
> Region hole contains wrong regions pair when hole is created by first region deletion
> -------------------------------------------------------------------------------------
>
> Key: HBASE-24916
> URL: https://issues.apache.org/jira/browse/HBASE-24916
> Project: HBase
> Issue Type: Bug
> Components: hbck2
> Affects Versions: 2.2.3
> Reporter: Ajeet Rai
> Assignee: Mohammad Arshad
> Priority: Major
>
> HBCK2 Holes: Wrong region details in HBCK report ,if a region is missing in meta and start key is empty
> for hole, it reports two region where hole is present.
> Scenario where first region is missing for eg: in below scenario r1 is missing in meta
> start key end key region
> empty 10 r1
> 10 20 r2
> 20 30 r2
> 30 empty r3
>
> In our test hbck report contains two region where first region belongs to different table and second region is r2.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)