ClickHouse versioning policy
ClickHouse has a frequent release policy. In Managed Service for ClickHouse, a limited set of ClickHouse versions is available, which is continually updated. If the ClickHouse version used in a Managed Service for ClickHouse cluster becomes obsolete, it gets updated.
Updating to current versions allows you to get new functionality, patches, and security fixes, which improves the overall stability of the cluster.
Each ClickHouse version supported by Managed Service for ClickHouse undergoes comprehensive testing.
You can be confident that your data will remain safe and accessible after updating to a new supported version of ClickHouse.
Version support policy for
Managed Service for ClickHouse uses two types of ClickHouse versions:
LTS (versions with extended support period, Long-Term Support).
The LTS version support period is 1 year, with new versions released every 6 months.
Two LTS versions are supported: the current one and the previous one.
When a new LTS version is released in Managed Service for ClickHouse, the oldest available LTS version stops being supported.
The three latest ClickHouse versions, including interim ones, are supported. If one of these versions is an LTS version, only two interim versions are supported.
When a new interim ClickHouse version is released in Managed Service for ClickHouse, the oldest interim version stops being supported.
You can manually change the cluster version to one of the supported versions.
- You can't create new hosts in clusters on a deprecated version of ClickHouse.
- Clusters on a deprecated version of ClickHouse are automatically updated according to the update policy.
A Managed Service for ClickHouse cluster on a deprecated version of ClickHouse is updated to the next LTS version.
Notifications about the scheduled update of clusters using a deprecated LTS version are sent to users 2 months and 1 week before the update.
A Managed Service for ClickHouse cluster on a deprecated ClickHouse version is updated to either an LTS version, if available, or the latest interim version.
- Notifications about the scheduled update of clusters using a deprecated interim version are sent to users 1 week before the update.
- If you upgrade to the LTS version, the corresponding update policy is applied to the cluster.