Automated monitoring with Pacemaker resource agents

Being There

Article from Issue 139/2012

When a cluster node fails, the Pacemaker high-availability tool launches the services on another node. A lesser known feature is Pacemaker’s ability to put failed services back on their feet in the cluster manager.

Pacemaker [1] has developed into the undisputed, standard high-availability solution for Linux systems. If one of two nodes in a cluster fails, Pacemaker launches the failed services on the other cluster node. But if you only use Pacemaker for failover actions, you are missing one of its best features. Many administrators are unaware that Pacemaker can automatically put failed applications back on their feet.

Buy this article as PDF

Express-Checkout as PDF
Price $2.95
(incl. VAT)

Buy Linux Magazine

Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • CoreOS

    CoreOS is an operating system for the cloud that relies on Docker and also lets you build compute clusters out of the box.

  • Linbit Becomes Heartbeat 2 Maintainer

    The Linbit firm out of Vienna will take over care of the Heartbeat 2 cluster manager.

  • Hyperic HQ

    Monitor a Java application server with Hyperic HQ.

  • RHEL 7

    On June 10, Red Hat launched a new major release of its enterprise distribution, RHEL 7. We take a look to find out where RHEL is headed.


    Iptables gives admins the ability to set up clusters and distribute the load. But what about failover?

comments powered by Disqus
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters

Support Our Work

Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

Learn More