Cloudera Docs

Preparing for an upgrade or responding to an upgrade failure

Learn about how to prepare for an upgrade or respond to an upgrade failure.

  1. Check if v5 is available in your region.
    Run the following command:
    az vm list-skus --location <region> --resource-type virtualMachines \
                   --size Standard_D8s_v5 --output table
  2. Check the Restrictions column.
    • If the Restrictions column is empty or shows None, v5 is available, no entitlement is needed, upgrade normally.
    • If the Restrictions column contains NotAvailableForSubscription, then v5 is blocked. Proceed to step 3.
  3. Decide which entitlement or entitlements need to be enabled.
    • If Node pools (AKS) are affected, enable the DE_AZURE_LEGACY_WORKLOAD_INSTANCE_TYPE entitlement.
    • If DB (MySQL Flexible Server) is affected, enable the DE_AZURE_LEGACY_DB_INSTANCE_TYPE entitlement.
  4. Trigger the upgrade.
    Migration components are skipped. The cluster upgrades to the new Cloudera Data Engineering version on existing instance types. Pre-flight check also completes successfully, no migration is planned and no validation is needed.
  5. When v5 capacity becomes available, perform the following operations:
    1. Disable the entitlements.
    2. Trigger a new upgrade.
    The migration then proceeds and updates the cluster to v5 instance types.