Hi Quanah
Please find my answers inline
a) Both servers have no DB, but are using these configs [Rahul] Both servers are started with an empty database. Both servers are in Provider and consumer mode. Our application is running on both servers as well. To start with our application is active on Server A, which means data will be written to server A database.and is synced/replicated to server B
b) DB is added to server A and replicated to server B [Rahul] Yes since server A has our application in active mode hence data is written on server A and replicated to server B.
c) server A is stopped [Rahul] yes we reboot the server A.
d) You say "data is removed", I'm not sure what this means. A single entry? Multiple entries? The entire database? [Rahul] Now our application is active on Server B. Using server B removed "a Single Entry" which was removed from server B database as well.
e) S1 is restarted, and the deleted data is replicated back to both nodes. [Rahul] Yes deleted data is replicated back to both nodes. when S1 is restarted slapd is configured in provider/consumer mode but our application is still active on server B which means writes will only happen at server B and should be synced to server A.
Thank you for all the help so far. I have no intention of interrupting your work. Please look at my issue based on your convenience.
Let me know if you have any other questions.
Thanks Rahul
On Tue, Jun 23, 2020 at 3:43 PM Quanah Gibson-Mount quanah@symas.com wrote:
--On Tuesday, June 23, 2020 1:47 PM -0400 kumar rahul rahul2002mit@gmail.com 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
--On Tuesday, June 23, 2020 5:04 PM -0400 kumar rahul rahul2002mit@gmail.com wrote:
Hi Quanah
Hi Kumar,
I was able to reproduce the issue, thanks for the report. I'll file a bug for it.
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
openldap-technical@openldap.org