Multi-Cluster Version Support

Multi-Cluster Version Support in LogScale requires running the same version across all clusters due to protocol compatibility requirements between systems sharing Multi-Cluster search information.

The multi-cluster protocol is not compatible across different versions of LogScale. Compatibility depends on the underlying protocol used for sharing Multi-Cluster search information between systems.

Important

In general, you should run the same (major and minor) version of LogScale on all clusters.

Multi-cluster search is available when the minimum compatible version matches the cluster where the view was created. Two versions are compatible if they have the same minimum compatible version.

Multi-Cluster Compatibility Across Versions

The multi-cluster protocol is not compatible across versions of LogScale. For this reason you must run the exact same version of LogScale on all clusters. The implementation checks that the versions match and data will be omitted from any remote clusters running a different version from the federating cluster.

If an exact version check is prohibitively strict there is a workaround, because LogScale releases occur more frequently than incompatible changes to the protocol. If you set this environment configuration:

ini
UNSAFE_RELAX_FEDERATED_PROTOCOL_VERSION_CHECK=true

This configuration permits some version incompatibility when versions are compatible at the protocol level. Each LogScale version has a minimum compatible version. This is the smallest version that is protocol-compatible with that version. Two versions are compatible if they both have the same minimum compatible version.

Two versions are compatible if they're both within the same LogScale LTS version. This means that compatibility is ensured when upgrading from one LTS version to the next one. Conversely, LogScale does not guarantee compatibility if there is an upgrade that skips one or more LTS versions.