Class not found exception while creating table in HBASE
After successfully installing and configuring HBase over HDFS on our local servers, I did the same configuration on our VVV VPS machines, however, I get a strange error.
The whole installation starts fine, however, when I try to create a table from the hbase shell, I get the following error:
2017-05-20 11: 59: 19,256 ERROR [RpcServer.FifoWFPBQ.default.handler = 29, queue = 2, port = 16000] master.MasterRpcServices: region server prdhad001,16020,1495274311971 reported fatal error: Server ABORTING region prdhad001 , 16020,1495274311971: coprocessor org.apache.hadoop.hbase.client.coprocessor.AggregateImplementation threw java.lang.ClassNotFoundException: org.apache.hadoop.hbase.client.coprocessor.Aggregate.ImplementationException: org.apache.hadoop.hbase.client.coprocessor.AggregateImplementation.Clap .hadoop.hbase.client.coprocessor.AggregateImplementation at java.net.URLClassLoader.findClass (URLClassLoader.java:381)
and after that the whole hbase becomes corrupted and throws numerous errors. It doesn't seem to load some jars properly, however the jar is present in the lib folder.
My configuration:
Virtualization: kvm Operating system: CentOS Linux 7 (Core)
CPE OS Name: cpe: / o: centos: centos: 7
Kernel: Linux 3.10.0-514.16.1.el7.x86_64
Architecture: x86-64 Hadoop 2.7 .3 HBase 1.3.0export PATH = $ PATH: export $ HADOOP_HOME / bin HADOOP_HOME = / usr / local / hasoop export PATH = $ PATH: $ HADOOP_HOME / bin
export PATH = $ PATH: export $ HADOOP_HOME / sbin HADOOP_MAPRED_HOME = $ Export HADOOP_HOMEHOME HADOOP_HDFS_HOME = $ HADOOP_HOME export YARN_HOME = $ HADOOP_HOME export HADOOP_COMMON_LIB_NATIVE_DIR = $ HADOOP_HOME / lib / native export HADOOP_OPTS = "- Djava.library.path = $ HADOOP_HOME / library
source to share
I realized, inside hbase-site.xml I got the following property:
<property>
<name>hbase.coprocessor.region.classes</name>
<value>org.apache.hadoop.hbase.coprocessor.AggregateImplementation</value>
</property>
which is used for a coprocessor that we are not currently using. However, after removing this part, I decided that if we want to use the coprocessor in the future, we might run into this problem again and any other help would be appreciated.
source to share