[
https://issues.apache.org/jira/browse/HBASE-21169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619781#comment-16619781
]
stack commented on HBASE-21169:
-------------------------------
bq. So lots of the recover code will still be in the hbase repo?
Yes. A basic tenet is that Master does the repairs.
bq. And HBCK2 is just a tool which asks HMaster to execute the recovery code?
Yeah. Hopefully we can figure a few generic tools that can be combined
variously to fix the sort of issues we could run into: finish-the-procedure,
assigns, unassigns...
bq. Maybe we need to introduce a new HBaseInterfaceAudience called HBCK to
indicate that this tool is used by HBCK2?
Makes sense. Adding. Filed HBASE-21209
> Initiate hbck2 tool in hbase-operator-tools repo
> ------------------------------------------------
>
> Key: HBASE-21169
> URL: https://issues.apache.org/jira/browse/HBASE-21169
> Project: HBase
> Issue Type: Sub-task
> Components: hbck2
> Affects Versions: 2.1.0
> Reporter: Umesh Agashe
> Assignee: stack
> Priority: Major
> Attachments: hbase-21169.master.001.patch
>
>
> Create hbck2 tool in hbase-operator-tools
> (https://github.com/apache/hbase-operator-tools.git) repo. This is not
> intended to be complete tool but initial changes with usage, ability to
> connect to server, logging, and using newly added HbckService etc. Code
> changes to address specific use cases can be added later and tool will evolve.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
