Tip/Trick of the Month: Using Highly Available Clusters with Red Hat Messaging

by Bruce Wolfe (Red Hat)

Red Hat Messaging (RHM) is built on top of the AMQP wire-level protocol, and is designed to be inherently reliable. However, if you have the resources, you can make your messaging application more robust with the addition of High Availability (HA) Clustering.

To set up a simple cluster you will need to edit three files, and populate the same values across each RHM broker and/or RHEL host instance:

/etc/corosync/corosync.conf

In the totem section add the network bind address (bindnetaddr), multicast address (mcastaddr), and multicast port (mcastport). For example, respectively: 192.168.10.0, 224.0.0.10, 5430

/etc/corosync/uidgid.d/qpidd

Make sure the user-id and group-id that the qpidd process is running under is populated correctly in this file. Default is: qpidd

/etc/qpidd.conf

Add cluster-name= to this file. For example: rhm-cluster

Generally, this requires corosync to be installed and running on each RHEL host, and that each RHM broker is configured identically (very minor exceptions allowed).

Start the brokers in your cluster and begin enjoying the benefits of HA Clustering.

Learn more about configuring and using HA Clustering in the all-new Red Hat Messaging Deployment (RHD355) course.

Creative Commons License
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s