[
https://issues.apache.org/jira/browse/HBASE-22723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896279#comment-16896279
]
stack commented on HBASE-22723:
-------------------------------
Fixing my mess. I'd tested master and branch-2 compile. Presumed branch-2
compile meant it good to go all the ways back. Duh.
For branch 2.2, I backported HBASE-22408 then re-reverted this patch (had to
make a one line change in the added test because method name was different in
MetaTableAccessor).
For re-backport to branch-2.1 and branch-2.0, removed the checkServers
method... That means the feature that ensures all servers mentioned in
hbase:meta are 'known' is missing in the branch-2.1/branch-2.0 backports.
> Have CatalogJanitor report holes and overlaps; i.e. problems it sees when
> doing its regular scan of hbase:meta
> --------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-22723
> URL: https://issues.apache.org/jira/browse/HBASE-22723
> Project: HBase
> Issue Type: Sub-task
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6
>
> Attachments: HBASE-22723.branch-2.001.patch,
> HBASE-22723.branch-2.002.patch, HBASE-22723.branch-2.003.patch,
> HBASE-22723.branch-2.004.patch, HBASE-22723.branch-2.005.patch,
> HBASE-22723.branch-2.006.patch, HBASE-22723.branch-2.007.patch
>
>
> CatalogJanitor scans hbase:meta on a configurable period. Currently it just
> looks for splits and merges to gc. Might as well generate a report on stuff
> like holds, overlaps, empty regioninfos, and unknown servers while it is at
> it.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
