[
https://issues.apache.org/jira/browse/HBASE-19121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663145#comment-16663145
]
Jingyun Tian commented on HBASE-19121:
--------------------------------------
[~stack]
I checked this doc
[https://github.com/apache/hbase-operator-tools/tree/master/hbase-hbck2], it's
very helpful.
I mean the onlineConsistencyRepair. The problem I met is that one server is
crash and SCP is not finished since I delete the procedure logs, then the
inconsistency come out. These regions are recorded as OPEN at that crashed
regionserver in META, that's why I need a tool to help find all these regions
that are OPEN in META but actually not alive anymore.
Canary tool can help solve this problem. But it's a little bit slow since it
needs to read a key from all these regions. As the Implementation of
onlineConsistencyRepair, we only need to compare the onlineRegions of META and
all the regions reported by all regionservers. So I'm not very sure if we still
need to port this one since canary tool can solve this.
Besides, do we still get a chance to met the problem that region OPEN on more
than one regionserver? I've never met but seems no tools can help find this
problem?
The biggest benefit of onlineConsistencyRepair I think is to show all these
inconsistency problems, then we operators can decide how to fix these problems.
{quote}That said, we could do with more operator help. I think tools to fix
hbase.version file and research to see if possible to rebuild a meta table if
for some reason meta were erased would be good to have.
{quote}
Yes, this could be put on schedule in case some extremely situation happens.
> HBCK for AMv2 (A.K.A HBCK2)
> ---------------------------
>
> Key: HBASE-19121
> URL: https://issues.apache.org/jira/browse/HBASE-19121
> Project: HBase
> Issue Type: Umbrella
> Components: hbck, hbck2
> Reporter: stack
> Assignee: Umesh Agashe
> Priority: Major
> Fix For: hbck2-1.0.0
>
> Attachments: hbase-19121.master.001.patch
>
>
> We don't have an hbck for the new AM. Old hbck may actually do damage going
> against AMv2.
> Fix.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
