sync repl uses the retro changelog to refresh a clien which provides a cookie. the changes since the cookie are retrieved form the retro changelog.
To maintain the retro changelog only for that purpose is an overhead and the retro changelog was also part in several deadlock situation.
All the information required by sync repl is also already available in the regular mmr changelog, but there is no api to access it from another plugin.
Investigate the possibility and cost to use the MMR changelog instead of Retro CL
Note: the priority 'minor' does not mean the severity of this bug is low.
Comment by Ludwig:
It would be good to have this to avoid problems with ReroCL in IPA and to have an additional backend. But it looks not trivial, would like to spend some time investigating. Maybe we can keep it in 1.3.5 and push out if too much effort.
Per triage, push the target milestone to 1.3.6.
Metadata Update from @nhosoi: - Issue set to the milestone: 1.3.6.0
Metadata Update from @mreynolds: - Issue close_status updated to: None - Issue set to the milestone: 1.4 backlog (was: 1.3.6.0)
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None - Issue tagged with: RFE
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.5 (was: 1.4 backlog) - Issue tagged with: Complex, Regression
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/1628
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 - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.