Feature Request - High avaliblity #52
Mati1060
started this conversation in
Feature Requests
Replies: 1 comment
-
Agreed! Comparable in its mechanics like keepalived (VRRP). You would have only one master at a time and steering the failover behavior via weights. And only the master is pushing updates to the slave(s). That would also require that the current slaves are locked for any changes. The only problem would be how to connect to backends? Easy just spin up three newt containers each connected to one of the pangolin containers. That in combination with a loadbalancer in front of the Pangolin instances would be killer! Cheers |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The ability to run multple "management server" that can all accept connections and then load balance them internally would be nice. Something akin to a cdn basically have one master server that you configure and that configuration is then pushed out to the slave servers. And then you could have either an anycast ip address or have the traffic be load balanced at a dns level between the servers.
This along side these 2 feture request are the only thing that are holding me back from switching my operation to using this tool
ODIC Integration
Load Balancing
Beta Was this translation helpful? Give feedback.
All reactions