Configuration changes on non-primary master nodes can cause unexpected behavior

In a clustered environment, there are certain configuration entries that should only be modified on the primary master.

This is mostly applicable to entries in the local management interface under Web > Global Settings and Global Keys.

Currently, it is not possible to automatically disable such actions or prevent changes from being made on non-primary master nodes. Any such changes however can be overwritten, deleted or modified during the next cluster replication operation. This in turn may lead to unexpected behavior like outages or other functional errors.

It is therefore recommended that configuration changes be made only on the primary master.

Parent topic: Troubleshoot on the appliance