You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Wellington Chevreuil (Jira)" <ji...@apache.org> on 2021/01/25 18:21:00 UTC

[jira] [Resolved] (HBASE-25266) [hbase-operator-tools] Add a repair tool for moving stale regions dir not present in meta away from table dir

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

Wellington Chevreuil resolved HBASE-25266.
------------------------------------------
    Resolution: Fixed

> [hbase-operator-tools] Add a repair tool for moving stale regions dir not present in meta away from table dir
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-25266
>                 URL: https://issues.apache.org/jira/browse/HBASE-25266
>             Project: HBase
>          Issue Type: New Feature
>          Components: hbase-operator-tools
>    Affects Versions: hbase-operator-tools-1.0.0
>            Reporter: Wellington Chevreuil
>            Assignee: Wellington Chevreuil
>            Priority: Major
>             Fix For: hbase-operator-tools-1.1.0
>
>
> This adds a new tool under *hbase-tools* module, that allows for moving aways regions dirs existing under table's hdfs dir, but not in meta. This is useful in cases where the region is not present in meta, but still has data on hdfs, yet no holes in the table region chain is detected. 
> On such cases, the existing *HBCK2 addFsRegionsMissingInMeta* command isn't ideal, as it would bring the region back in meta and cause overlaps. 
> This tool performs the following actions:
> 1) Identifies regions in hdfs but not in meta using *HBCK2.reportTablesWithMissingRegionsInMeta*;
> 2) For each of these regions, sidelines the related dir to a temp folder;
> 3) Bulkload hfiles from each sidelined region to the related table;
> Sidelined regions are never removed from temp folder. Operators should remove those manually, after they certified on data integrity. 



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