#48225 fractional replication needs a better handling of ruvs
Closed: wontfix None Opened 7 years ago by lkrispen.

If a replication agreement uses fractional replication by excluding and stripping attributes, this can lead to a situation where modifications are only local.
The local ruv is updated and maxcsn is increasing, but since none of the changes is replicated (skipped in the replication session), the consumer ruv is not updated.
The next replciation sessions always will start at the same old maxcsn in the consumer ruv and will iterate through the changlog - doing nothing.

This is the same issue as in ticket #48266, closing as duplicate

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

5 years 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/1556

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 (was: Duplicate)

2 years ago

Login to comment on this ticket.