[
https://issues.apache.org/jira/browse/HBASE-19121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663338#comment-16663338
]
Jingyun Tian commented on HBASE-19121:
--------------------------------------
{quote}Queu'ing an SCP is not enough (IIRC) because we don't have the list of
what regions were on that old dead server so when the SCP goes to do assigns,
it'll have an empty queue.
{quote}
Yes. That's why I proposed to port onlineConsistencyRepair. I think the steps
to fix these inconsistency problem could be as follows:
# Use tools to find problematic regions (inconsistency between META and
regionservers)
# Check if these problematic regionservers' WAL directory have -splitting
suffix. If so, a SCP need to be scheduled to split logs.
# After SCP done, reassign problematic regions we get from step 1.
bq. Adding some functionality to the Canary where it recognizes that the server
is not online, is not in dead servers, and perhaps has no WALs on fs, might be
the way to go? You'd add a flag for it to actually act on any Regions it found
that were in the 'wrong' state? Its sort of built to do this sort of review of
the cluster?
Do you mean let Canary tool to check if the region is OPEN on META but
regionserver is not found? Then let Canary to gather all these information and
we operator fix problems base on those information?
Thanks.
> 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)
