ADD/DEL received during total update can be missing in the changelog of initilaized replica

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49000

• Created at 2016-10-05 17:53:36 by lkrispen (@elkris)
• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1377730

---

If a server receives updates while performing a total update (more exactly between sending the supplier RUV and building the idlist for entries to send) these updates can be part of the database and will be sent in the total init butthey are newer than the RUV sent.

After the total init is completed the consumer side of the init set its RUV (== sent supplier RUV), then the incremental protocal starts and will send updates newer than the RUV, including the updates already sent in the init.

On the consumer side ADDs and DELs will be ignored:

[05/Oct/2016:11:45:11 +0200] conn=7 op=4 csn=57f4cc96000200640000 - urp_add (cn=xx-186,ou=People,dc=example,dc=com): an entry with this uniqueid already exists.
[05/Oct/2016:11:45:11 +0200] conn=7 op=5 csn=57f4cc98000000640000 - urp_add (cn=xx-187,ou=People,dc=example,dc=com): an entry with this uniqueid already exists.
[05/Oct/2016:11:45:12 +0200] conn=7 op=6 csn=57f4cc98000100640000 - urp_add (cn=xx-188,ou=People,dc=example,dc=com): an entry with this uniqueid already exists.
[05/Oct/2016:11:45:12 +0200] conn=7 op=7 csn=57f4cc98000200640000 - urp_add (cn=xx-189,ou=People,dc=example,dc=com): an entry with this uniqueid already exists.
[05/Oct/2016:11:57:06 +0200] conn=14 op=4 csn=57f4cf60000000640000 - urp_delete: Entry "nsuniqueid=53865a69-8ae011e6-ab8d8005-8430f734,cn=xx-179,ou=People,dc=example,dc=com" is already a Tombstone.
[05/Oct/2016:11:57:06 +0200] conn=14 op=5 csn=57f4cf60000100640000 - urp_delete: Entry "nsuniqueid=53865a67-8ae011e6-ab8d8005-8430f734,cn=xx-178,ou=People,dc=example,dc=com" is already a Tombstone.
[05/Oct/2016:11:57:06 +0200] conn=14 op=6 csn=57f4cf61000000640000 - urp_delete: Entry "nsuniqueid=53865a65-8ae011e6-ab8d8005-8430f734,cn=xx-177,ou=People,dc=example,dc=com" is already a Tombstone.

this means they will not be written to the changelog, and can be missing csns in a replication session originating from this consumer.

The probabilty for these kind of changes might be low, but we also do it systematically when creating "keep alive" entries.

[389-ds-bot]

Comment from lkrispen (@elkris) at 2017-02-11 22:58:05

Metadata Update from @elkris:

• Issue set to the milestone: 1.3.5.14

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2017-04-20 16:37:59

@elkris - Is your recent work on replication conflicts going to address this by any chance?

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2017-04-20 16:38:09

Metadata Update from @mreynolds389:

• Issue close_status updated to: None

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2017-05-24 17:11:07

Metadata Update from @mreynolds389:

• Issue set to the milestone: 1.3.6.0 (was: 1.3.5.14)

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2017-07-05 17:41:54

Metadata Update from @mreynolds389:

• Issue set to the milestone: 1.3.7.0 (was: 1.3.6.0)

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2019-08-23 20:31:19

Metadata Update from @mreynolds389:

• Custom field reviewstatus adjusted to None
• Issue set to the milestone: 1.4.2 (was: 1.3.7.0)

[389-ds-bot]

Comment from vashirov (@vashirov) at 2020-03-18 16:17:45

Metadata Update from @vashirov:

• Issue priority set to: minor (was: major)
• Issue set to the milestone: 1.4 backlog (was: 1.4.2)

[tbordaz]

Looking like an "issue" correctly handled by the consumer (ignoring the updates) so closing the ticket