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... > 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 hbase@node2:~/hbase-2.2.0$ hbase version HBase 2.2.0 Source code repository git://hao-OptiPlex-7050/home/hao/open_source/hbase revision= Compiled by hao on 2019年 03月 07日 星期四 14:05:34 CST >From source with checksum 783fee467bb1b28666f0d904437862c4 hbase@node2:~/hbase-2.2.0$ hbase Usage: hbase [<options>] <command> [<args>] Options: --config DIR Configuration direction to use. Default: ./conf --hosts HOSTS Override the list in 'regionservers' file --auth-as-server Authenticate to ZooKeeper using servers configuration --internal-classpath Skip attempting to use client facing jars (WARNING: unstable results between versions) Commands: Some commands take arguments. Pass no args or -h for usage. shell Run the HBase shell hbck Run the HBase 'fsck' tool. Defaults read-only hbck1. Pass '-j /path/to/HBCK2.jar' to run hbase-2.x HBCK2. snapshot Tool for managing snapshots wal Write-ahead-log analyzer hfile Store file analyzer zkcli Run the ZooKeeper shell master Run an HBase HMaster node regionserver Run an HBase HRegionServer node zookeeper Run a ZooKeeper server rest Run an HBase REST server thrift Run the HBase Thrift server thrift2 Run the HBase Thrift2 server clean Run the HBase clean up script classpath Dump hbase CLASSPATH mapredcp Dump CLASSPATH entries required by mapreduce pe Run PerformanceEvaluation ltt Run LoadTestTool canary Run the Canary tool version Print the version regionsplitter Run RegionSplitter tool rowcounter Run RowCounter tool cellcounter Run CellCounter tool pre-upgrade Run Pre-Upgrade validator tool CLASSNAME Run the class named CLASSNAME > > > > > Because the META is now assigned, I changed 1588230740 to 1431292037213 > to > > get the namespace table assigned. No idea how the meta got assigned... I > > removed /hbase from ZK, maybe it helped. > > > > It's not good that we're bouncing around states without knowing why > those states are changing. Let's focus on getting hbck2 invocations to > work as expected before continuing with cluster health. > Good for me. > > > Cluster is still running in maintenance mode: > > <property> > > <name>hbase.master.maintenance_mode</name> > > <value>true</value> > > </property> > > > > I don't recall suggesting maintenance mode and would suggest not being > in it for now. > Wellington suggested it earlier. Removing it for now.
