New answers tagged

0

It seems you only have two nodes, you'd want to add this: quorum { provider: corosync_votequorum expected_votes: 2 }


0

After several tries without success, I've tried again but this time creating the network share in the same wizard and now it magically worked.


1

in totem section, you can try to add this line: rrp_mode: none If it still has error, try to add more this section: quorum { provider: corosync_votequorum expected_votes: 3 }


0

you can also "simulate" the local network by doing iptables redirect from a local machine to remote cloud.


1

The normal way to handle multi-site fail over is to have a pair of load balancers on site A in a master/slave fail over config. Then put an identical pair on the remote site. If ALL the backend servers on site A fail then use the public VIP on site B as the fallback (high latencey of course across the WAN)... But back this up with a proper DNS based load ...


0

Stupid me. --swarm-discovery was not pointing to the right node :-( Needs to point to the existing master.


1

don't use the wrong tool haproxy is a wonderful tool. It does not provide caching. A quick scan of the fine docs can verify this. Unless you want to patch haproxy you need to use a tool that does what you're looking to do. don't create impossible problems By asking for haproxy to do something that it doesn't and excluding the tool that seems to do what ...



Top 50 recent answers are included