[
https://issues.apache.org/jira/browse/HBASE-23180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995224#comment-16995224
]
Sakthi commented on HBASE-23180:
--------------------------------
Also I would want to shift the focus of this Jira towards a standalone tool to
start with rather than a nightly job/Jenkins. I can add follow on for that,
once this goes in.
> Create a nightly build to verify hbck2
> --------------------------------------
>
> Key: HBASE-23180
> URL: https://issues.apache.org/jira/browse/HBASE-23180
> Project: HBase
> Issue Type: Task
> Reporter: Sakthi
> Assignee: Sakthi
> Priority: Major
> Labels: hbck2
> Fix For: hbase-operator-tools-1.1.0
>
>
> Quoting myself from the discussion thread from the dev mailing list "*How do
> we test hbck2?*" -
> "Planning to start working on a nightly build that can spin up a
> mini-cluster, load some data into it, do some actions to bring the cluster
> into an undesirable state that hbck2 can fix and then invoke the hbck2 to see
> if things work well.
>
> Plan is to start small with one of the hbck2 commands and remaining ones can
> be added incrementally. As of now I would like to start with making sure the
> job uses one of the hbase versions (probably 2.1.x/2.2.x), we can discuss
> about the need to run the job against all the present hbase versions/taking
> in a bunch of hbase versions as input and running against them/or just a
> single version.
>
> The job script would be located in our operator-tools repo."
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
