(removing 389-devel list from reply, this is probably better on the 389-users list :) )
We don't have tables per-say. We don't have these because there are many factors
involved that you need to consider when designing this kind of topology.
For example, what rate of changes do you expect to be incoming? How much latency and
bandwidth exists between the replicas? How many replicas do you want to deploy? How much
latency are you willing to tolerate between the nodes becoming consistent?
We are aware of a number of deployments that have high rates of change (thousands of
writes per second) that are replicating between continents (ie US/EU). However they also
have high bandwidth/low latency links between these locations to assist this.
So I think there are more questions to answer here about your potential deployment and
your specific concerns you have.
On 7 Oct 2020, at 07:24, 389ds(a)lemiere.org wrote:
do you have tables estimating the reasonable distance to synchronize two 389 directories
between two sites. Are there tables of recommendations depending on the distance?
What software tools or scripts allow evaluating it.
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
Senior Software Engineer, 389 Directory Server
SUSE Labs, Australia