This is great progress. :)
On Tue, Mar 12, 2019 at 5:39 PM Jean-Marc Spaggiari <[email protected]> wrote: > > Thanks for looking at it. Results are below. > > JMS > > Le mar. 12 mars 2019 à 18:16, Sean Busbey <[email protected]> a écrit : > > > > > > The hbase hbck -j ~/hbase-hbck2-for-2.2.0.jar unassigns 1588230740 > > command > > > doesn.t seems to be correct. "-j" is not a valid parameter, should be > > -jar. > > > And fixing it displayes the previous HBCK version help. > > > > > > > Okay, something is still wrong then. The cli option is definitely "-j" > > and not "-jar". > > > > Which "hbase" command is being run? > > > Ha, good point! I had hbase 2.0.0-beta in my path. Some sometimes I was > typing bin/hbase (which was making sure hbase 2.2.0 was running) and > sometimes hbase. I changed the path and it seems to like the -j parameter > better... > > hbase@node2:~/hbase-2.2.0$ hbase hbck -j > test/hbase-operator-tools/hbase-hbck2/target/original-hbase-hbck2-1.0.0-SNAPSHOT.jar > Error: A JNI error has occurred, please check your installation and try > again > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/commons/cli/ParseException > > Trying to figure why... > your command above points at the wrong jar from the hbck2 repo. it's pointing at the one where you need to manually assemble all the dependencies it has. You want the one that does not say "original" in the name. > > > Can you confirm it's the one in > > the bin tarball? what does the version command output? What does the > > mapredcp command output? What does the cli help for the hbase command > > show? > > > > hbase@node2:~/hbase-2.2.0$ hbase mapredcp > /home/hbase/hbase-2.2.0/bin/../lib/shaded-clients/hbase-shaded-mapreduce-2.2.0.jar:/home/hbase/hbase-2.2.0/bin/../lib/client-facing-thirdparty/audience-annotations-0.5.0.jar:/home/hbase/hbase-2.2.0/bin/../lib/client-facing-thirdparty/commons-logging-1.2.jar:/home/hbase/hbase-2.2.0/bin/../lib/client-facing-thirdparty/findbugs-annotations-1.3.9-1.jar:/home/hbase/hbase-2.2.0/bin/../lib/client-facing-thirdparty/htrace-core4-4.2.0-incubating.jar:/home/hbase/hbase-2.2.0/bin/../lib/client-facing-thirdparty/log4j-1.2.17.jar:/home/hbase/hbase-2.2.0/bin/../lib/client-facing-thirdparty/slf4j-api-1.7.25.jar > that looks great now. Once you correct the hbck2 jar above I think you'll be good for invoking HBCK2. Next, what does the initializing master say it's doing? It should be on the master UI near the bottom. If it hasn't made progress since your last update it'll be waiting for the hbase:namespace table. If it is, find the region and see what the last few messages in the master log are about that region.
