Contents

Online upgrades

About 5 minUpdated 2026-10-28

Both the controller and nodes are upgraded from System › System Upgrade in the panel. You don't need to re-run the install command.

Upgrade the controller

Open the controller tab of System › System Upgrade, check the current and available versions, and click Upgrade Master. If the page says the controller needs a restart afterwards, restart it as prompted.

Tip Before upgrading, check whether the release notes mark the version as requiring a restart, and schedule it for a quiet period.

Upgrade nodes

Node upgrades support staged rollout and one-click upgrade: upgrade a few nodes first and extend to the rest once they look healthy. You can also turn on "Auto-upgrade nodes when the Master is upgraded", so nodes follow the controller.

A node upgrade replaces the whole package: the new version is unpacked into its own directory and switched in atomically. If the new config fails its check, or nginx isn't ready after restart, the node switches back to the old version and keeps serving, and the upgrade is recorded as failed. The previous version is kept, and Roll back in the panel switches to it any time.

Re-running the installer also upgrades

Re-running the controller's install command also upgrades it to the newest version on the release site. The command is unchanged and existing data is untouched.

Caution The one-click controller upgrade only replaces the controller program and its config; it does not upgrade ClickHouse. ClickHouse is upgraded only when the install script is re-run.

If a license problem shows up during an upgrade, see Licenses and add-ons.