[
https://issues.apache.org/jira/browse/HBASE-30462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi updated HBASE-30462:
----------------------------------
Fix Version/s: hbase-operator-tools-1.4.0
Release Note: Fixed `extraRegionsInMeta` and `reportMissingRegionsInMeta`
misreporting regions of tables whose name or region start keys contain a `.`
(for example ns:my.table, or start keys like com.example). Previously, healthy
regions of such tables were reported as having no matching region directory,
and `extraRegionsInMeta --fix` would delete them from hbase:meta. If you ran
`extraRegionsInMeta --fix` on such tables with an earlier version, run
`addFsRegionsMissingInMeta` with this version to re-add any removed regions,
then assigns with the encoded region names it prints.
Resolution: Fixed
Status: Resolved (was: Patch Available)
Merged to master. Thanks for the review, [~paksyd] and [~nihaljain]!
> [hbase-operator-tools] HBCK2 extraRegionsInMeta fails on dots in table name
> or start key
> ----------------------------------------------------------------------------------------
>
> Key: HBASE-30462
> URL: https://issues.apache.org/jira/browse/HBASE-30462
> Project: HBase
> Issue Type: Bug
> Components: hbase-operator-tools
> Reporter: Peter Somogyi
> Assignee: Peter Somogyi
> Priority: Blocker
> Labels: pull-request-available
> Fix For: hbase-operator-tools-1.4.0
>
>
> HBCK2 extracts a region's encoded name from its hbase:meta row key by taking
> the text between dots wherever they appear in the key. When a table name or
> start key contains a ., the extracted name is wrong.
> extraRegionsInMeta then reports healthy regions as extra, and with -f it
> deletes them from meta. The fix is to take the encoded name from the end of
> the row key.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
