--On Tuesday, June 23, 2020 1:47 PM -0400 kumar rahul
<[email protected]> wrote:
Both the servers are set up as master as well as consumer so that
sync works in both directions. So
the sync setup is like "A -> B",
and when A fails B is updated and the expectation is that "B -> A" should
work because a multi master setup is already in place. Let me know based
on the attached configuration files if my assumption is correct or not.
Also Add data works when A fails and B is updated then sync "B -> A"works
fine.
After Delete data sync does not work when A fails and data is deleted
from B. Once A comes back both databases have data which was deleted on B.
Hi,
I'll see if I can reproduce your issue with the configs provided (Assuming
they look correct after I finish reviewing them in full), but I want to
confirm the exact steps:
a) Both servers have no DB, but are using these configs
b) DB is added to server A and replicated to server B
c) server A is stopped
d) You say "data is removed", I'm not sure what this means. A single
entry? Multiple entries? The entire database?
e) S1 is restarted, and the deleted data is replicated back to both nodes.
Note that I do have a paid job that keeps me busy, so this is a best effort
when I have time available to investigate.
Thanks,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
