The state of a replica is its RUV. It is sometime possible to give a clear status: R1 is ahead to R2, R1 is equivalent to R2.
In case of mixed status (R1 knowns updates that R2 does not and also the opposite), the tool could also loop for few sec. to check if it is progressing and could later lead to a clear status (e.g. suggest to retry later).
Dumping the RUV requires DM, so it could also check if there is fractional replication.
N/A
Currently ds-replcheck reports the difference between entries in replicas. It checks the data status (that can be expensive) but not the replication status (that would be much faster)
Enhance ds-replcheck or a new CLI
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 1.3.8
Metadata Update from @mreynolds: - Issue assigned to mreynolds
Fixed in:
https://pagure.io/389-ds-base/pull-request/50055
Metadata Update from @mreynolds: - Assignee reset - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
851fcf8..d808e3d 389-ds-base-1.3.9 -> 389-ds-base-1.3.9
Fix usage error:
c51748d..2671222 389-ds-base-1.3.9 -> 389-ds-base-1.3.9
Commit c6ad848 relates to this ticket
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/3087
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.