On 21 Aug 2012, at 22:06, David Lang <[email protected]> wrote: > > One legitimate reason for doing this is that you can then have heartbeat > 'monitor' the webserver and if the webserver dies, initiate a failover. > However > I think this is better done by having a dummy service that takes no time to > start/stop and implements it's status with a file and then have some other, > more > extensive monitoring system checking your web front end (checking that it > actually works, not just that apache is running) and altering the status file > that heartbeat checks. > > Or you can have your monitoring software send a message to heartbeat to > trigger > a failover.
Well haproxy does all that out of the box, no tricks or tweakery required. For monitoring services within a single server, I'm finding monit works well. If a web server server fails, haproxy will see that (from outside) and stop sending it traffic, and monit (on the server) will give it a kick and send appropriate notifications. That setup has coped with most of the problems that have come my way to date. Another thing I like about haproxy is that it's unnervingly fast; start/stop/reload are effectively instantaneous. I often find that crm_mon and heartbeat services take ages to do anything, and it's never clear whether it's just taking a long time or if something's wrong. I'm running heartbeat + pacemaker/crm at the moment. I've had a couple of attempts at migrating to corosync, but so far I've had no success and a great deal of confusion, even though all I'm doing is managing a single IP. As Dmitri said, heartbeat has other strengths, especially when it comes to more complex clusters with multiple services and dependencies, and the power can't be denied! Marcus -- Marcus Bointon Synchromedia Limited: Creators of http://www.smartmessages.net/ UK info@hand CRM solutions [email protected] | http://www.synchromedia.co.uk/ _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
