That did it! I pulled down:
https://www.apache.org/dyn/closer.lua/hbase/2.4.7/hbase-2.4.7-src.tar.gz
and built the software in maven using Java 8.
mvn package assembly:single -Dhadoop.profile=3.0
-Dhadoop-three.version=3.2.2 -DskipTests
I took the gz file from:
/hbase-2.4.7/hbase-assembly/target/
Keeping Hadoop client libraries in sync is one of those things which,
within a major version, is not likely to cause you problems. However, if
you are having a problem, that is the first thing I would do.
If you're in that territory, it's also a good idea to recompile HBase
against that exact
Thanks for the response. They are not. Hadoop 3.2.2 is running 3.2.2 libs,
while HBase is using the 2.10 Hadoop libs. Do these need to be in sync?
I did try syncing them up and adding 3.2.2 libs into HBase, replacing all
of the hadoop-* files and I got this error:
Unhandled: Found interface org.a
Are the Hadoop JARs which you're using inside HBase the same as the
Hadoop version you're running? (e.g. in $HBASE_HOME/lib)
On 10/15/21 6:18 PM, Damillious Jones wrote:
Hi all, I am seeing a similar issue which is noted in HBASE-26007 where
HBase will not start if dfs.encrypt.data.transfer in
Hi all, I am seeing a similar issue which is noted in HBASE-26007 where
HBase will not start if dfs.encrypt.data.transfer in HDFS is set to true.
When I start HBase I see the following error message on the master node:
java.io.IOException: Invalid token in javax.security.sasl.qop:
at
org.a
