Recovering from failed upgrades
If a Data Lake upgrade fails and you are unable to manually troubleshoot the problem, you may be able to use the recovery process to return the cluster to its pre-upgrade state.
Use the CDP CLI to recover the Data Lake after a failed upgrade:
cdp datalake recover-datalake --datalake-name <value> [--recovery-type <value>]
Name or CRN of the Data Lake that you want to recover after a failed upgrade.
The type of the recovery. The default value is RECOVER_WITHOUT_DATA.
Currently, the option RECOVER_WITH_DATA is not supported.The status of the Data Lake appears as "Datalake recovery in progress. Recovery process takes a while as the nodes are being terminated and new nodes are launched with the original runtime."
- Restore the Data Lake from the pre-upgrade backup. For more information, see Restore Data Lake content.
- If necessary, run the
cdp datalake sync-component-versions-from-cmcommand from the CDP CLI.
When an upgrade fails, the versions of Cloudera Manager, Runtime, and other components may become out-of-sync with the CDP Management Console. Similarly, if you try to fix errors by installing parcels manually, it may not be reflected in the CDP Management Console.
To overcome the mismatch between versions reflected in the Management Console, run the
cdp datalake sync-component-versions-from-cmCDP CLI command. This commands reads the CM, Runtime, and other parcel versions (if applicable) from CM and updates the versions in the CDP Management Console. Using this command forces the CDP Management Console back in sync so that it shows the actual versions installed in CM.
cdp datalake sync-component-versions-from-cm --datalake-name <datalake name>