Support Questions
Find answers, ask questions, and share your expertise

org.apache.phoenix.coprocessor.SystemCatalogRegionObserver cannot be loaded

org.apache.phoenix.coprocessor.SystemCatalogRegionObserver cannot be loaded

New Contributor

using hbase version 2.1 

pheonix version  5.1.1 

 

using following dependencies 

compile('org.apache.phoenix:phoenix-core:5.1.1') {
exclude module: 'sqlline'
exclude module: 'slf4j-log4j12'
}
compile('org.apache.phoenix:phoenix-hbase-compat-2.2.5:5.1.1')

 

getting following error 

Caused by: org.springframework.jdbc.CannotGetJdbcConnectionException: Failed to obtain JDBC Connection; nested exception is org.apache.phoenix.exception.PhoenixIOException: org.apache.hadoop.hbase.DoNotRetryIOException: Class org.apache.phoenix.coprocessor.SystemCatalogRegionObserver cannot be loaded Set hbase.table.sanity.checks to false at conf or table descriptor if you want to bypass sanity checks
at org.apache.hadoop.hbase.master.HMaster.warnOrThrowExceptionForFailure(HMaster.java:2228)
at org.apache.hadoop.hbase.master.HMaster.sanityCheckTableDescriptor(HMaster.java:2075)
at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1974)
at org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:636)
at org.apache.hadoop.hbase.shaded.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:413)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:132)
at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:324)
at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:304)

at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:81)
at org.mybatis.spring.transaction.SpringManagedTransaction.openConnection(SpringManagedTransaction.java:82)
at org.mybatis.spring.transaction.SpringManagedTransaction.getConnection(SpringManagedTransaction.java:68)
at org.apache.ibatis.executor.BaseExecutor.getConnection(BaseExecutor.java:336)
at org.apache.ibatis.executor.SimpleExecutor.prepareStatement(SimpleExecutor.java:84)
at org.apache.ibatis.executor.SimpleExecutor.doUpdate(SimpleExecutor.java:49)
at org.apache.ibatis.executor.BaseExecutor.update(BaseExecutor.java:117)
at org.apache.ibatis.executor.CachingExecutor.update(CachingExecutor.java:76)
at org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.java:198)
... 83 more
Caused by: org.apache.phoenix.exception.PhoenixIOException: org.apache.hadoop.hbase.DoNotRetryIOException: Class org.apache.phoenix.coprocessor.SystemCatalogRegionObserver cannot be loaded Set hbase.table.sanity.checks to false at conf or table descriptor if you want to bypass sanity checks
at org.apache.hadoop.hbase.master.HMaster.warnOrThrowExceptionForFailure(HMaster.java:2228)
at org.apache.hadoop.hbase.master.HMaster.sanityCheckTableDescriptor(HMaster.java:2075)
at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1974)
at org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:636)
at org.apache.hadoop.hbase.shaded.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:413)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:132)
at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:324)
at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:304)

 

1 REPLY 1

Re: org.apache.phoenix.coprocessor.SystemCatalogRegionObserver cannot be loaded

Expert Contributor

Hello @gurucgi 

 

This is an Old Post yet we wish to check if the issue has been addressed by you. If Yes, Please share the Steps to ensure fellow Community Users can benefit from your experience. 

 

Based on the Post, SystemCatalogRegionObserver is being reported for Class not being loaded. The concerned Error is being received for Phoenix v5.1.1. In Cloudera, We are shipping with Phoenix v5.1.0 at the time of writing. I am not sure if you are being impacted via [1]. In short, the JAR seems to be requiring the Phoenix-Server Jar to be placed rightfully. 

 

- Smarak

 

[1] https://issues.apache.org/jira/browse/PHOENIX-6330