[ 
https://issues.apache.org/jira/browse/HBASE-21215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663229#comment-16663229
 ] 

stack commented on HBASE-21215:
-------------------------------

I built hbck2 as follows:

{code}
$ mvn install -DskipTests -Dhbase.version=3.0.0-SNAPSHOT
{code}

Built master hbase like this:
{code}
$ mvn clean install -DskipTests assembly:single
{code}

Undid tarball and go this:
{code}
$ ./bin/hbase version
HBase 3.0.0-SNAPSHOT
Source code repository git://kalashnikov.local/Users/stack/checkouts/hbase 
revision=614612a9d8b38ea1b8b960ee9ff55e90c09e45e1
Compiled by stack on Wed Oct 24 21:10:40 PDT 2018
>From source with checksum 8b7e8b92143b96c4b6509e19c292ff8d

$  ./bin/hbase hbck -j 
~/checkouts/hbase-operator-tools/hbase-hbck2/target/hbase-hbck2-1.0.0-SNAPSHOT.jar
  --version
project.version=1.0.0-SNAPSHOT
git.commit.id=dd8a0e285eb52d9d6862efc30610f8a529f8ceea
git.build.version=1.0.0-SNAPSHOT
{code}

There is something in here but I'm not triggering it. Will keep at it.

> Figure how to invoke hbck2; make it easy to find
> ------------------------------------------------
>
>                 Key: HBASE-21215
>                 URL: https://issues.apache.org/jira/browse/HBASE-21215
>             Project: HBase
>          Issue Type: Sub-task
>          Components: amv2, hbck2
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0, 2.1.1, 2.0.3
>
>         Attachments: HBASE-21215.branch-2.1.001.patch, 
> HBASE-21215.branch-2.1.002.patch, HBASE-21215.branch-2.1.003.patch, 
> HBASE-21215.branch-2.1.004.patch, HBASE-21215.branch-2.1.005.patch
>
>
> In 
> https://docs.google.com/document/d/1Oun4G3M5fyrM0OxXcCKYF8td0KD7gJQjnU9Ad-2t-uk/edit#,
>  the doc on hbck2 'form', one item to figure is how to invoke hbck2. Related, 
> how to make it easy to find? [~busbey] has some ideas (posted in doc). This 
> issue is for implementation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to