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

Hive canary health check failed for an unknown reason

Hive canary health check failed for an unknown reason

New Contributor

 

We are running Hive (version 3.1.3000) Metastore through Cloudera runtime (version 7.1.1-1.cdh7.1.1.p0.3266817). We are running the metastore database on Postgres 10. Even though Hive service successfully generated the metastore tables on the database, canary health check keeps failing.

Following is the from the metastore log:

INFO audit
[pool-7-thread-104]: ugi=hive	
ip=xx.xx.xx.xxx cmd=Done cleaning up thread local RawStore
ERROR TThreadPoolServer
[pool-7-thread-105]: Thrift error occurred during processing of message.
org.apache.thrift.protocol.TProtocolException: Missing version in readMessageBegin
, old client? at org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin
(TBinaryProtocol.java:228) ~[hive-exec-3.1.3000.7.1.1.0-565.jar:3.1.3000.7.1.1.0-565] at org.apache.hadoop.hive.metastore.TUGIBasedProcessor.process
(TUGIBasedProcessor.java:76) ~[hive-exec-3.1.3000.7.1.1.0-565.jar:3.1.3000.7.1.1.0-565] at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run
(TThreadPoolServer.java:286) [hive-exec-3.1.3000.7.1.1.0-565.jar:3.1.3000.7.1.1.0-565] at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1149) [?:1.8.0_262] at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:624) [?:1.8.0_262] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_262]

 

replaced our ip with xx.xx.xx.xxx

 

We checked that the metastore service is listening in on port 9083. So, not sure why the health check keeps failing. Any help is appreciated.