We’ve been bitten by positioning active-replica
statement at the end of config file instead where it is by default. Everything seemed to behave ok, even the clients seemed like to be able to connect. Still, our application behaved abnormally. Also, the active-replica
statement was configured before the replicaof
. Our KeyDB version is 6.0.18 (AlmaLinux 8).
Also, the wording on active replica configuration on this issue seems somewhat ambiguous:
Note: When setting up multi-master in a config file, make sure to enable multi-master
and active-replica
BEFORE setting your replicaof
commands, as shown in the examples below, otherwise multi-master replication may not work correctly.
This could be also understood as configuration in steps and not positioning in the configuration file:
- configure/enable
multi-master
andactive-replica
and restart service - configure
replicaof
and restart service
Could someone enlighten me on this topic?