#47986 Recovered supplier need to reject direct update until it is in sync with the topology
Closed: wontfix a year ago by spichugi. Opened 6 years ago by tbordaz.

The problem is that if a recovered supplier accepts direct updates before being in sync, replica to that supplier and from that supplier is broken.

Use case in MMR with two suppliers M1/rid1 and M2/rid2

ldif RUV is : [ rid1_t0, rid2_t1]

T20:
M1 RUV is [rid1_t5, rid2_t6]
M2 RUV is [rid1_t5, rid2_t6]

M1 is recovered from the ldif file

T21:
M1 RUV is [rid1_t0, rid2_t1]
M2 RUV is [rid1_t5, rid2_t6]

T22:
ldapclient send update to M1
M1 RUV is [rid1_t22, rid2_t1]
M2 RUV is [rid1_t5, rid2_t6]

T23
M2 starts a replication session to M1, It will update M2 with updates [rid2_t1..rid2_t6]
M1 RUV is [rid1_t22, rid2_t6]
M2 RUV is [rid1_t5, rid2_t6]

But here replication is broken both ways. M2 does not know rid1_t22 in its CL and can not update M1. After the import, M1 CL has been cleared, so M1 does not know rid1_t5 and can not update M2.

This problem exist with ldif recovery but I think it also exists with backup recovery.


Comments made in the ticket triage:
Ludwig: should be done, but is change in behaviour, sjould be configurable.
Thierry: if configurable, what would be the default behavior: reject/accept.

Per triage, push the target milestone to 1.3.6.

Metadata Update from @nhosoi:
- Issue set to the milestone: 1.3.6.0

4 years ago

Metadata Update from @mreynolds:
- Issue close_status updated to: None
- Issue set to the milestone: 1.4 backlog (was: 1.3.6.0)

4 years ago

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.4.4 (was: 1.4 backlog)
- Issue tagged with: Replication

a year ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1317

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata