[
https://issues.apache.org/jira/browse/HBASE-21966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16805548#comment-16805548
]
Sean Busbey commented on HBASE-21966:
-------------------------------------
Some notes from a discussion [~elserj] and I ended up having after a customer
escalation:
{quote}
We liked the idea
of making very focused operations, rather than sweeping "-repair"
options, e.g. "create a row in hbase:meta for this regiondir", "create
an empty regiondir", "create a regiondir from this hbase:meta row".
With tools like this, you could imagine a CLI tool stepping through
the Regions of a table presenting a three-way merge like tool: for
every region in a table, ask the user if they want to keep the state
in meta or the state in HDFS. We like this idea because it keeps HBase
devs out of the role of figuring out what the correct thing to do is.
A couple of related concerns:
* Such a tool would not aim to be sufficient for the bar some folks have
expressed for HBck2 to move the "stable" pointer to HBase 2. Essentially some
ability to rebuild meta from external info ala HBASE-21665 or HBASE-18840
* Need to make sure these tools are compose-able. It's all
well-and-good to say that human-insight needs to be applied to know
what HBCK2 commands to run, but we also don't want cluster recoveries
to take 10's of hours. Something easily scriptable is important. To continue
the three-way-merge analogy, merge strategies ala ours/theirs in git.
{quote}
> Fix region holes, overlaps, and other region related errors
> -----------------------------------------------------------
>
> Key: HBASE-21966
> URL: https://issues.apache.org/jira/browse/HBASE-21966
> Project: HBase
> Issue Type: Sub-task
> Reporter: Jingyun Tian
> Assignee: Jingyun Tian
> Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
