Issue 7755 - not replicated nodes after recovery
Summary: not replicated nodes after recovery
Status: VERIFIED SUSPENDED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: 2.4.38
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-27 05:26 UTC by dmitrii.fonariuk@gmail.com
Modified: 2020-03-20 17:49 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description dmitrii.fonariuk@gmail.com 2013-11-27 05:26:46 UTC
Full_Name: Dmitrii Fonariuk
Version: 2.4.38
OS: RHEL6.x86_64
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (91.210.4.1)


hi.

I have two servers in Multi-Master mode (type=refreshAndPersist)

1.	I add's one DN (DN=1) on first node, after replication i see DN=1 on both
nodes. 
2.	I've done backup via mdb_copy on 1st node.
3.	After that i add's one DN on 2nd node (DN=2) and one DN on 1st node (DN=3).
4.	I see DN=1, DN=2, DN=3 on both nodes and the same contextCSN.
5.	I stop the slapd on 1st node and do recovery from last backup.
6.	Start slapd.
7.	Now I see DN=1, DN=2, DN=3 on 2nd node and DN=1, DN=2 on 1nd node and the
same contextCSN. 

Why DN=3, added after backup on 1st node doesn't replicated from 2nd node?

if i on 6 step start slapd with -c rid=001 - all OK. (performed long time if a
lot of data)
if i on 6 step before start slapd change his serverID on different value - all
OK. (not suitable)

I can conclude that the back is not replicated that DN, entryCSN value that
matches the value serverID.

This is a bug or a feature?
Comment 1 Quanah Gibson-Mount 2019-04-19 17:00:04 UTC
--On Wednesday, November 27, 2013 5:26 AM +0000 dmitrii.fonariuk@gmail.com 
wrote:

> Full_Name: Dmitrii Fonariuk
>
> I can conclude that the back is not replicated that DN, entryCSN value
> that matches the value serverID.
>
> This is a bug or a feature?

Hello,

This would be a bug.  However, it's most likely fixed since the 2.4.38 
release, as there have been numerous replication related fixes since that 
time.

If you can reproduce this issue with the current OpenLDAP release, please 
let us know.  I apologize for the length in time in responding to this 
report.

Regards,
Quanah


--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>


Comment 2 OpenLDAP project 2019-04-19 17:00:27 UTC
likely fixed in the 5+ years since this was filed.
Comment 3 Quanah Gibson-Mount 2019-04-19 17:00:27 UTC
changed notes