4

Monitoring Varnish with Heartbeat and Pacemaker

view full story
linux-howto

http://serverfault.com – 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. This bit works fine. What I haven't accounted for is if Varnish isn't running on either server. It's currently possible to stop Varnish without triggering any sort of action from Heartbeat/Pacemaker. I'd like the absense of an operational (HowTos)

dayu's picture
Submitted by dayu on 07/24/2012 – Made popular on 07/24/2012

Stories similar to Monitoring Varnish with Heartbeat and Pacemaker

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.

We use Varnish as our front-end web cache and load balancer, so we have a Linux server in our development environment, running Varnish with some basic caching and load-balancing rules across a pair of Windows 2008 IIS web servers.

We have a wildcard DNS rule that points *.development at this Varnish box, so we can browse http://www.mysite.com.development, http://www.othersite.com.development, etc

I've been tying to install Heartbeat3.0.5+Pacemaker1.0.12 on CentOS 6.3 64bit via yum.

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.

Varnish/HaProxy/Nginx 30 weeks 6 days ago

Could you tell me if a configuration as below looks ok to serve pages delivered from my web servers. Is there some difficulty?

Requests --> HaProxy --> Varnish --> Nginx (frontend web server).

Is-it better to install varnish on my load balancers (haproxy) or on my web servers?

Cheers and thanks!

ApacheBooster 42 weeks 3 days ago

ApacheBooster is a integration of nginx and varnish, this Plugin will reduce the server load spike and memory usage. Also the plugin will provide the maximum performance of your websites.

Varnish

Varnish Cache is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents.

I have the following setup:

I have configured high availability between two load balancers (HAProxy) so that if HAProxy1 get down, the floating IP gets transferred to the other load balancer HAProxy2, hence all the clients will get the response from HAProxy2, which at the back-end is doing LB among the sme two webserver.

If I have two web servers, what would the best way to keep their files in sync?

Unfortunately the sites themselves cannot be altered significantly. Most of them are Wordpress based, but there are over 200 of them. There are also some custom sites.

This setup is going from Web server + DB Server to Varnish load balancer + 2x web servers + DB Server.

I have got e.g. two servers with Apache and Postfix and a virtual IP (from heartbeat-1). Well, heartbeat is working well and it is simple to deal with complete server outages, but how can I configure heartbeat, so that it also switches the server, if one of the above services fail?