Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.1.0
-
None
Description
Problem: During Rolling Upgrade, if Hive Metastore fails to restart, even after clicking Retry, Ambari cannot restart Hive Metastore. This situation can occur if Hive Metastore is using an external database (such as Oracle).
Solution: During Rolling Upgrade, if Hive Metastore fails to restart, even after clicking Retry in the Rolling Upgrade Wizard, Ambari cannot restart Hive Metastore and displays the following error in Ambari:
resource_management.core.exceptions.Fail: Execution of 'cp /usr/hdp/current/hive-metastore/lib/ojdbc.jar /usr/hdp/2.3.2.0-2943/hive/lib' returned 1. cp: '/usr/hdp/current/hive-metastore/lib/ojdbc.jar' and '/usr/hdp/2.3.2.0-2943/hive/lib/ojdbc.jar' are the same file
In order to get Hive Metastore to restart, before clicking Retry again, go onto the Hive Metastore host and move HDP version back to the original.
hdp-select set hive-metastore <original-hdp-version>
After performing the hdp-select, click Retry and proceed with the Rolling Upgrade.
Attachments
Attachments
Issue Links
- links to