CDP Public cloud (Azure/AWS) clusters - Hive is not working

[#1]

Hi Team,

Since couple of days we are finding issues in CDP Public Cloud clusters of both Azure and AWS , where Hive service is not working.

Issue happening for both existing and newly deployed clusters. Please find the error message below.

ERROR:

ERROR HiveMetaStore
[main]: MetaException(message:java.io.IOException: org.apache.knox.gateway.shell.ErrorResponse: https://xxxx.xxxx.cloudera.site:8444/gateway/dt/knoxtoken/api/v1/token: HTTP/1.1 500 Server Error)
Caused by: org.apache.hadoop.service.ServiceStateException: java.io.IOException: org.apache.knox.gateway.shell.ErrorResponse: https://xxxxx.xxxx.cloudera.site:8444/gateway/dt/knoxtoken/api/v1/token: HTTP/1.1 500 Server Error

[#2]

Hi Team,

We have been experiencing an issue shortly after cluster deployment. While the environment creation—including Data Lake, Data Hub, and ID Broker mapping—completes successfully, the Hive service subsequently goes down with a shared error.

The most recent deployments attempted were:

CDP AWS Public Cloud 7.2.17 – High Availability (HA)
CDP Azure Public Cloud 7.2.18 – High Availability (HA)

ERROR:
ERROR HiveMetaStore
[main]: MetaException(message:java.io.IOException: org.apache.knox.gateway.shell.ErrorResponse: https://xxxx.xxxx.cloudera.site:8444/gateway/dt/knoxtoken/api/v1/token: HTTP/1.1 500 Server Error)
Caused by: org.apache.hadoop.service.ServiceStateException: java.io.IOException: org.apache.knox.gateway.shell.ErrorResponse: https://xxxxx.xxxx.cloudera.site:8444/gateway/dt/knoxtoken/api/v1/token: HTTP/1.1 500 Server Error

Attaching the screenshot of Hive metastore log containing the error message.

[#3]

Hi @Jaguar ,

This issue seems to be related with Knox.

Service Mismatch: The URL in the error (.../gateway/dt/knoxtoken/api/v1/token) suggests a conflict between the Hive Metastore and the Knox Token Service. This often happens after a cluster upgrade where a new token service is implemented, but the clients (in this case, the Metastore) are still configured for the old one.

• Solution: Check the Knox configuration in your cluster management tool (e.g., Cloudera Manager). Verify that the HiveServer2 and Hive Metastore services are using the correct Knox topology and that the token service settings are correctly configured to match the Knox server.

Let me know if this helps.