If the anchorcsn determined for starting a replication session cannot be found replication stops. This can happen if eg a hub was initialized and further initialized a consumer, depending on the contents of the RUV and the sequence of changes applied to the masters after initialization.
There was a fallback implemented to pick "a" csn as anchorcsn in this case (based on the supplierRUV), which would ensure that the csn is found but would potentially miss changes between the required and the used csn.
This erroneous fallback was removed with the fix for: #48766 and not replaced
attachment 0001-Ticket-48954-replication-fails-because-anchorcsn-can.patch
Setting the target milestone to 1.2.11.33.
Ludwig, could you please push your fix to master, 389-ds-base-1.3.4 and 389-ds-base-1.2.11?
Thanks! --noriko
committed to master:
ldap/servers/plugins/replication/cl5_clcache.c | 32 +++++++++++- ldap/servers/plugins/replication/repl5_replica.c | 58 +++++++++++++++-------- 2 files changed, 67 insertions(+), 23 deletions(-)
New commits: commit 0721856
to 1.3.4: commit c72a14f
to 1.2.11: commit 08b0ee8
Hi Ludwig,
Is it ok to close this ticket? ;)
Thanks!
Metadata Update from @lkrispen: - Issue assigned to lkrispen - Issue set to the milestone: 1.2.11.33
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/2013
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.