11

How to run multiple Heartbeat/Corosync/Pacemaker clusters in the same network? (Quorum)

view full story
linux-howto

http://serverfault.com – We intend to run several components to run a web site. Like a load balancer, a cache and a couple of web serserves. To avoid single-points-of-failure we intended to use Heartbeat/Corosync/Pacemaker and instead of one load balancer just run two of them. Now we have different choices how we set them up and I would like to hear your opinion which one works better: Run pairs of servers in different clusters. E.g. "loadbalancer1" and "loadbalancer2". That way we wouldn't have two few servers to reach quorum if one of the servers failed. We could switch off the quorum feature though but would risk (HowTos)

grtyyu's picture
Submitted by grtyyu on 02/13/2012 – Made popular on 02/13/2012

Stories similar to How to run multiple Heartbeat/Corosync/Pacemaker clusters in the same network? (Quorum)

I'm having trouble figuring out how to configure a 2-node setup with a third simpler one for quorum.

It seems to think all the nodes have the capability to act as a full fallback node, when I only I want a quorum with STONITH working sanely for what is essentially a 2+1 DRBD-MySQL node system.

Any tips or documentation on how to make the 3rd node just a quorum member would be appreciated.

I have a pair of servers setup as high availability load balancers/reverse proxies. Each runs Ubuntu 12.04 x64 Server, Varnish, Heartbeat and Pacemaker, with Varnish load balancing traffic to back-end servers.

If either of the load balancers falls over, Heartbeat/Pacemaker transfers a group of virtual IPs over to the other server, and traffic flow resumes.

I am using Haproxy to load balance replicated mysql master servers. I am also using Heartbeat and Pacemaker for Active/Active ip failover with two virtual ips on the two load balancers for web server high availability. I used location in pacemaker to stay VIPs one on each load balancer and I'm using round-robin DNS domains pointing to VIPs to load balance the load balancers.

Setting Up A High-Availability Load Balancer (With Failover and Session Support) With HAProxy/Heartbeat On Debian Lenny

I'm setting up a load balancer with failover and I'm confused on how to properly set it up. The load-balancer is balancing web traffic to web-servers on a LAN network.

My setup is the following:

I have one incoming external IP address, that ethernet cable goes to a switch. One output from the switch is going to load_balancer_1 and the second output going to load_balancer_2.

quorum disk configuration issue 2 years 37 weeks ago

Hi,All;

Some stuff confused me when I configurated the quorum disk. I read the related documents abouth the quorum disk and I do not understand completely.

I have 3 servers, 1 as load balancer and 2 as web-servers(apache tomcat) hosting some jsp pages.

This seems like a simple question, but one I can't seem to find the answer for despite going over the pacemaker documentation multiple times.

I've got corosync set up with pacemaker to share a virtual IP. All I want to do is to set a timeout value before the backup node takes over the resource.

We're building a load balanced setup with two load balancers (that also terminate SSL) and several upstream servers. Both the load balancers and the upstream servers run nginx. The network on which requests are forwarded to the upstream servers cannot be trusted, hence we have to re-encrypt it after SSL termination on the load balancer.