- Who we are
- What we know
- What we've created
- Hints and Kinks
- Checking Corosync cluster membership
- Configuring radosgw to behave like Amazon S3
- Downgrading to DRBD 8.3
- Fencing in Libvirt/KVM virtualized cluster nodes
- Fencing in VMware virtualized Pacemaker nodes
- GFS2 in Pacemaker (Debian/Ubuntu)
- Interleaving in Pacemaker clones
- Maintenance in active Pacemaker clusters
- Managing cron jobs with Pacemaker
- Mandatory and advisory ordering in Pacemaker
- Migrating virtual machines from block-based storage to RADOS/Ceph
- Network connectivity check in Pacemaker
- OCFS2 in Pacemaker (Debian/Ubuntu)
- Solid-state drives and Ceph OSD journals
- Solve a DRBD split-brain in 4 steps
- Testing Pacemaker clusters
- Totem "Retransmit List" in Corosync
- Turning Ceph RBD Images into SAN Storage Devices
- Which OSD stores a specific RADOS object?
- Die eigene Cloud mit OpenStack Essex (German, LinuxTag 2012)
- Fencing (LCE 2011)
- GlusterFS in HA Clusters (LCEU 2012)
- GlusterFS und Ceph (German, CeBIT 2012)
- Hands-On With Ceph (LCEU 2012)
- High Availability Update (OpenStack Summit Fall 2012)
- High Availability in OpenStack (CloudOpen 2012)
- High Availability in OpenStack (OpenStack Conference Spring 2012)
- Highly Available Cloud: Pacemaker integration with OpenStack (OSCON 2012)
- Mit OpenStack zur eigenen Cloud (German, CLT 2012)
- Mit OpenStack zur eigenen Cloud (German, OSDC 2012)
- More Reliable, More Resilient, More Redundant (OpenStack Summit April 2013)
- MySQL HA Deep Dive (MySQL Conference 2012)
- MySQL High Availability Deep Dive (PLUK 2012)
- MySQL High Availability Sprint (PLUK 2011)
- OpenStack Essex im Praxistest (German, Linuxwochen Wien 2012)
- OpenStack High Availability Update (Grizzly and Havana)
- Roll Your Own Cloud (LCA 2011)
- Storage Replication in HPHA (LCA 2012)
- Zen of Pacemaker (LCA 2012)
- Technical documentation
- News releases
- Hints and Kinks
- What we do
- What we charge
- What others say
Heartbeat is an alternative to Corosync for the cluster communications layer. Like Corosync, it constitutes the "lower" half of the high-availability stack (the "upper" half is cluster resource management, such as Pacemaker).
We have built and run Heartbeat clusters for years and know its capabilities inside and out. Whether you are planning a no-downtime migration to Corosync, or an upgrade of existing legacy systems, we'll be happy to help.
What's it good for?
Heartbeat is a solid cluster communication manager for small to medium-sized clusters of up to 8 nodes. It supports communications via UDP broadcast, unicast or multicast. Pacemaker supports Heartbeat out of the box in Ubuntu and Debian GNU/Linux. For SLES and RHEL, custom Pacemaker packages are needed; these, however, are obviously unsupported by the system vendors.
For high-availability Pacemaker configurations with cluster file systems such as OCFS2 or GFS2, Heartbeat is not an option. Heartbeat-based Pacemaker clusters do not support Distributed Lock Manager (DLM) integration.
If I run on Heartbeat, do I need Pacemaker?
Legacy versions of Heartbeat contain a simplistic resource manager that should no longer be used. We can assist you in a smooth transition.
Can I migrate my Pacemaker cluster?
If your Pacemaker cluster runs on Heartbeat and you'd like to move to Corosync, we can assist you in the migration. It's even possible without interruption to your cluster services.
If you're experiencing issues with Heartbeat, we can help rapidly. We can offer a wide array of Heartbeat consulting services. Talk to one of us within the next 15 minutes. Ask The Expert Now!