I'm attempting to replace our nodejs <-> redis production config with keydb as we have a need for multi-master syncing across datacenters. We're running 2x docker swarm currently with 1 redis replica per site via docker-ce (so the swarms act independently and don't know about each other).
Question: Is the only way to do this
--replicaof=<opposite potential nodes> or is there a better way to do this?
Trying to prevent a single point of failure here without having to specify every potential node in every site or having to rearchitect this with haproxy or keepalived.
Appreciate any insights into this as it seemd to work, but the "unavailable" replicas spam the logs with:
Unable to connect to MASTER: Resource temporarily unavailable
Essentially, does this add any unnecessary overhead by specifying unavailable masters that might hamper the performance if it remains in this state? If not, is there anyway to suppress this output? :)
I think I had a misconfiguration in ansible, as it stopped spamming once I fixed the right host groups and redeployed.
I did notice that if I didn't set both the master password & "default" password the same, I was getting
Unable to AUTH to MASTER: -WRONGPASS invalid username-password pair but that could be again due to the previous misconfiguration with ansible. I haven't gone back to try different passwords; if it's required you may want to make that clearer in the example as I had tried two different credentials and was getting that error. I'll test in a few just to be sure, probably pebkac.
Appreciate the quick responses!
--masterauth blahw/ a
--masterpassword fooand a
--requirepass barappears to break things in multi-master. No biggie since we have a pretty simple setup, but would be nice to have different default credentials, assuming nothing slows down. I have not tried setting a specific non-default user to see if there is a difference, but it's not worth messing around with right now. Thanks again!