Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

HiveServer2Error: ImpalaRuntimeException: Error making 'add_partitions' RPC to Hive Metastore

avatar
New Contributor

I converted non-ha hadoop cluster to ha hadoop cluster using below article

https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.0.0/fault-tolerance/content/deploying_namenode_ha_...

 

After conversion, getting "HiveServer2Error: ImpalaRuntimeException: Error making 'add_partitions' RPC to Hive Metastore" exception while trying to upload file

 

What can cause this problem ?

1 ACCEPTED SOLUTION

avatar
New Contributor

Thanks. I was able to resolve it by updating the location in hive meta store.

/usr/bin/hive --service metatool -updateLocation new-location old-location

View solution in original post

2 REPLIES 2

avatar
Expert Contributor

The error message "HiveServer2Error: ImpalaRuntimeException: Error making 'add_partitions' RPC to Hive Metastore" typically indicates a problem when Impala, a distributed SQL query engine, tries to interact with the Hive Metastore service to add partitions. This error can be caused by several factors, and it usually points to an issue with the Hive Metastore service or the interaction between Impala and Hive. Here are some common causes and troubleshooting steps for this error:

  1. Hive Metastore Service Issues:

    • Check if the Hive Metastore service is up and running. You should ensure that the Hive Metastore service is started and healthy.
    • Verify that the Hive Metastore service is reachable from the machine where Impala is running. Network issues or firewall rules could prevent proper communication.
  2. Metastore Configuration:

    • Verify the Metastore configuration in the Impala configuration files (impala-site.xml). Ensure that the Metastore URIs and authentication settings are correctly configured.
  3. Metastore Database Issues:

    • Check the health and availability of the underlying database used by the Hive Metastore. Ensure that it's accessible, and there are no database connection issues.
    • Verify that the Metastore database is not overwhelmed or experiencing performance problems.
  4. Authorization and Authentication:

    • Verify that the Impala service has the necessary privileges and permissions to interact with the Hive Metastore.
    • Check if Kerberos authentication is enabled, and ensure that the necessary credentials and keytabs are correctly configured.
  5. Log Analysis:

    • Examine the logs of both Impala and Hive Metastore services for more detailed error messages. The logs may provide additional information about the root cause of the issue.
  6. Resource Limitations:

    • Check if there are any resource limitations (e.g., memory, CPU) on the machines running Impala and the Hive Metastore. Resource shortages can lead to RPC failures.
  7. Software Versions:

    • Ensure that Impala and Hive are compatible in terms of versions and dependencies. An incompatible combination of software versions can lead to errors.
  8. Cluster Issues:

    • If you are running Impala in a distributed cluster, verify the overall health of the cluster. Other cluster-level issues can sometimes affect the interaction with the Hive Metastore.
  9. Network Issues:

    • Check for network-related problems, such as DNS resolution or proxy settings, which can impede communication between Impala and the Hive Metastore.
  10. Database Locks:

    • Database locks in the Metastore can sometimes cause issues. Check if there are any locks in the Hive Metastore database.

If you have access to detailed logs or additional error messages, those can be particularly helpful in diagnosing the specific problem that led to this error. Depending on your environment and configurations, the resolution may involve addressing one or more of the above factors.

avatar
New Contributor

Thanks. I was able to resolve it by updating the location in hive meta store.

/usr/bin/hive --service metatool -updateLocation new-location old-location