Skip to content

Upgrades

Move a cluster to a newer Kafka or RabbitMQ version in place. Upgrades are one-way.

Updated View as Markdown

Patch releases within a version are applied in the cluster’s maintenance window. Moving to a newer version, such as Kafka 4.3 to 4.4, is your choice:

ezgh hosted-queues clusters engine-versions
ezgh hosted-queues clusters upgrade hqc_4k2m9x0a7qpe --engine-version 4.4 --wait

In the console, it’s Upgrade on the cluster’s page. The cluster is upgrading and keeps serving: a replicated cluster moves one node at a time, and the next only once the cluster is fully healthy again. Connections to the node moving close, and clients reconnect (see Timeouts and reconnects). When every node is on the new version, the cluster turns on the new version’s features.

Upgrades are one-way: a cluster can’t go back to an older version, and a downgrade is refused with 409 downgrade_not_supported. If an upgrade can’t complete, its operation fails; run it again to finish.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close