-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Geo-Cluster questions #175
Comments
Hi @Orsopepe, The latency here will be the main issue for both PostgreSQL replication and Corosync. I don't have experience or documentation in regard to geo clusters. However, I've seen various discussions related to them on Pacemaker user mailing list. It is usually about increasing some timeouts in corosync configuration and/or setting up Booth: https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Explained/ch15.html Regards, |
PS: do not hesitate to report here the result of your research! |
Sorry for the late answer, i will let you know any kind of solution im going to test! |
Hi @Orsopepe I know I'm quite late to the party but I've done geo patches to PAF some time ago as I've been also designing the geo-ha: https://github.com/YanChii/PAF/tree/master-geo-ha Jan |
Hi Guys,
I was asked to build a geographic cluster with automatic failover that replicates on 3 server rooms located on the same country.
the internet that connects them is 100mb/s.
I immediately discarded the Patroni cluster as too sensitive to network latencies and network speeds.
I know that PAF supports Geo Replication but I havent found any kind of information about it.
Thanks for your support
Pepe
The text was updated successfully, but these errors were encountered: