Skip to content
LogScale Self-Hosted
This is an archived version of the documentation downloaded from LogScale Documentation Archives. Up to date documentation, and documentation for later versions, is available on LogScale Documentation

## `UNSAFE_RELAX_FEDERATED_PROTOCOL_VERSION_CHECK`

Option | `UNSAFE_RELAX_FEDERATED_PROTOCOL_VERSION_CHECK`
Description | Permits version discrepancy across clusters in Multi-Cluster Search, provided that the versions are compatible at the protocol level.
Introduced Version | 1.124
Removed in Version | 1.195
Default | `false`

### Removed: Configuration variable v1.195

Due to the removal of server compatibility checks from multi-cluster searches, `UNSAFE_RELAX_FEDERATED_PROTOCOL_VERSION_CHECK` is also being removed.

In LogScale Multi-Cluster Search, because the multi-cluster protocol is not compatible across versions of LogScale, the exact same version of LogScale must be run on all clusters, with the system checking that the versions match. However, for cases where the exact version match is prohibitively strict, it is possible to bypass this rule by setting the following configuration:

ini

    UNSAFE_RELAX_FEDERATED_PROTOCOL_VERSION_CHECK=true

It will allow for version discrepancy across clusters, provided that the versions are compatible at the protocol level.

The whole implementation as well as this workaround configuration are explained in more detail at Multi-Cluster Version Support.

#### Enter search term