On 6/30/25 11:25 AM, Paul Dekkers wrote:
There is replication via sync_client and sync_server; it's rolling replication, asynchronous, and not explicitly advertised as bi-directional, but in my experience you can setup a master-replica relation in both directions in particular if you send client-traffic to one at a time (like with a haproxy that has a preferred server and does pollig). Maybe the latter is over cautious, but at least that's how I felt confident enough to use it ;-)
I'm confused about the difference between using master-replication in the simpler case and your "over cautious" case?
For example, in the non-"over cautious" case, what happens when the master connects to the other server and it discovers a change on the other server? Does that change get synced back? (Perhaps in practice but not advertised so?)
In my current Dovecot setup the master only does a replication when the master has a change to make on the other server, but any changes it discovers on the other server will get synced back. Yes, there can be a delay if the master has no activity, but that's reasonable..
Is this how Cyrus's replication works? Thanks, -kb ------------------------------------------ Cyrus: Info Permalink: https://cyrus.topicbox.com/groups/info/T0c0e25e570f21952-M9da36017838d309087b2e409 Delivery options: https://cyrus.topicbox.com/groups/info/subscription
