I'm a greenhorn when it comes to clustering in RHEL/CentOS and recently setup an active/standby clustering using Apache & Heartbeat. It seems to be a good entry step into clustering however after testing it I was disappointed in that the resource manager does not start httpd on node2 if httpd on node1 is dead (only starts httpd on node2 if the heartbeat daemon on node1 is dead). Is there anyway to achieve this setup if not with Heartbeat with some sort of other HA solution? Thank you! Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100217/369bb5b9/attachment.html>
On Wed, 2010-02-17 at 10:27 -0600, Dan Burkland wrote:> I?m a greenhorn when it comes to clustering in RHEL/CentOS and > recently setup an active/standby clustering using Apache & Heartbeat. > It seems to be a good entry step into clustering however after testing > it I was disappointed in that the resource manager does not start > httpd on node2 if httpd on node1 is dead (only starts httpd on node2 > if the heartbeat daemon on node1 is dead). Is there anyway to achieve > this setup if not with Heartbeat with some sort of other HA solution?(Bear in mind - I'm talking about Heartbeat V1 config style here, not v2/3.) I've used mon successfully to enable that. You can add mon as a clustered resource in addition to apache, then configure mon to look for the apache process. If it finds that httpd isn't running, it will kill the heartbeat process, thereby forcing a failover. In Heartbeat V2/3, I believe that pacemaker does something similar, though I'm not certain, as I'm mortally allergic to xml-based config files that have been massively overbuilt. ;) -I
On 2/17/2010 10:27 AM, Dan Burkland wrote:> I?m a greenhorn when it comes to clustering in RHEL/CentOS and recently > setup an active/standby clustering using Apache & Heartbeat. It seems to > be a good entry step into clustering however after testing it I was > disappointed in that the resource manager does not start httpd on node2 > if httpd on node1 is dead (only starts httpd on node2 if the heartbeat > daemon on node1 is dead). Is there anyway to achieve this setup if not > with Heartbeat with some sort of other HA solution?You can write your own service test(s) that would trigger failover (or just restart the failed service...). Just do a 'service heartbeat stop' if you want the primary to hand off to the backup quickly. -- Les Mikesell lesmikesell at gmail.com