[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
replication issue with MDB in ldapadd
- To: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
- Subject: replication issue with MDB in ldapadd
- From: Gurjot Kaur <gurjot.kaur@aricent.com>
- Date: Fri, 15 Jul 2016 09:39:36 +0000
- Accept-language: en-US
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=gurjot.kaur@aricent.com;
- Content-language: en-US
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aricent.onmicrosoft.com; s=selector1-Aricent-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=LHMtJng/9aMJR0GR71vxiUSvec1/0hEkRkdN5iKK860=; b=VdeaIeMya6BrFjO0K8g5RFb+O+273Bfl5TLl2r+ixJ8XJ9zHuAOw/UNn4X8o+r7OA4V4dnBNJAtkhH9yuQk97u8nGOq1Z80WQIHHC+4HOYNjsIS4CDHYMeCdNE/Qvg+MVsk3YGAubwU1csx2TZ+BQh4dNIwqZBHNKo6NBJJILQw=
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
- Thread-index: AdHebe7VLLxW2nxiTlymwUy5jTwUHw==
- Thread-topic: replication issue with MDB in ldapadd
Hello,
I have encountered with a problem in OpenLDAP2.4.44 with MDB backend.
I have two LDAP servers in Multi Master Mode MM1 and MM2. I am doing the following steps:
1. Both the LDAP DBs MM1 and MM2 have existing LDIF entries.
2.Start MM1. Stop MM2.
3. Add an entry A to MM1 using ldapadd. Stop MM1.
4. Start MM2. Add LDIF entry B to MM2 using ldapadd.
5. Start MM1.
I am getting the below result.
The last added entry i.e. B in MM2 gets replicated to MM1. But LDIF entry A doesn't get replicated to MM2.
But this scenario works fine in OpenLDAP 2.4.11 with BDB backend. It replicates entry A to MM2 and entry B to MM1 correctly.
How the above scenario with MBD in 2.4.44 can be avoided? As this is very common scenario.
Thanks
Gurjot Kaur
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."