Rolling upgrade limitations
Consider the following points while performing a rolling runtime and an operating system upgrade of a COD cluster.
Operating system upgrade limitations
- An unwanted rolling OS upgrade can be triggered if a runtime upgrade is not available,
resulting in COD downtime. Ensure that the runtime upgrade is available for the selected
runtime using the cdp opdb describe-upgrade-database command before
using the following command.
cdp opdb upgrade-database --environment <environment-name> --database <database-name> --runtime <runtime-version> --rolling-upgrade
- COD rolling upgrade is focused on HBase and Phoenix thick clients excluding Phoenix Query Servers (PQS) because PQS connectivity depends on Knox which is not deployed in HA mode. When Knox is unavailable during the upgrade, PQS, HBase REST and other endpoints connected through Knox can be interrupted.
- The Cloudera Runtime and operating system rolling upgrades are currently supported for COD clusters whose storage is selected as HDFS or cloud without ephemeral storage.
