389-ds-base

#48381 detect if replica is coming online
Closed: wontfix by spichugi. Opened by lkrispen.

Closed: wontfix
Reopen Issue

In the replication protocol the replication thread goes to backoff if the replica cannot be reached, it increases the backoff interval up to a maximum.

During IPA installation the new replica is frequently restarted and the replication of changes can be delayed quite long.

It would be good if a server could detect that a replica is no longer offline and get out of the backoff state.

One scenario is when the remote server opens a replication connection to the local server - then the remote server is online.

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 set to the milestone: 1.4.5 (was: 1.4 backlog)

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/1712

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)
Metadata
None
None
None
None
High
IPA
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.