You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I can gather patroni still supports one sync replica. I have a situation where would like to deploy to k8s cluster which has a controlplane spanning data centres. I need to guarantee zero data loss when a DC is lost.
Ideally I would have one three databases per DC with a sync replica at each site. Ideally a failover would prefer a local replica (although this isn’t a requirement).
Worst case just one sync replica at the other site. Obviously a failover complicates matters as if a DC was down just a single local replica would do.
Do I have any chance of making this work?
The text was updated successfully, but these errors were encountered:
There is WiP patch #672 which implements quorum commit and allows having more than one sync replica, it will partially solve your issue. Unfortunately it doesn't provide a way to specify in which DC you would like to have sync replicas. So one should also make Patroni dc-aware and implement the ability to specify priorities.
I don't really have time for that, any contributions are welcomed.
From what I can gather patroni still supports one sync replica. I have a situation where would like to deploy to k8s cluster which has a controlplane spanning data centres. I need to guarantee zero data loss when a DC is lost.
Ideally I would have one three databases per DC with a sync replica at each site. Ideally a failover would prefer a local replica (although this isn’t a requirement).
Worst case just one sync replica at the other site. Obviously a failover complicates matters as if a DC was down just a single local replica would do.
Do I have any chance of making this work?
The text was updated successfully, but these errors were encountered: