Skip to content

MQ High Availability Architectures: In-Region Active Active


Work in Progress


Audience: Architects, Application developers, Administrators

In this topic, we're going to:

  • review the essential elements of what provides NativeHA high-availability to the latest versions of IBM MQ
  • understand the impact at the infrastructure, services, and application tiers which a multi-instance, high-availability requirement brings
  • discuss in-region, multi-instance deployment characteristics and needs
  • deploy this topology to your OpenShift cluster

Architecture Overview


The following components comprise the high-availability topology at a high level. As your desired topology evolves to reduce single points of failure, this list will become more robust in nature.

  1. Virtual Private Cloud:

    • Distribute workloads across a minimum of three (3) sets of infrastructure service resources in 3 distinct availability zones (AZ).
  2. Red Hat OpenShift Container Platform:

    • Minimum two (2) OpenShift Compute Nodes per AZ to achieve standard OpenShift SLOs (99.99% possible).
  3. IBM MQ - Native HA Queue Manager:

    • Requires a minimum of one (1) OpenShift Node in each AZ for normal mode operations.
    • Requires a minimum of two (2) OpenShift Nodes in each AZ during OpenShift Node maintenance.
    • Requires a Uniform Cluster with at least two unique Queue Manager instances as members.
  4. MQ Client Application:

Single Points of Failure

These services and infrastructure components have been identified as potential single points of failure in this topology:

  1. Red Hat OpenShift Container Platform
  2. Regional Cloud Networking
  3. Regional Cloud Storage
  4. Regional Cloud Ingress/Egress

The Queue Manager has been removed from this list (first established in the In-Region Active Passive - Single Points of Failure section), as there are now multiple Queue Manager instances deployed in unison as a Uniform Cluster.

Infrastructure Requirements

This topology, as it extends the simplest topology which still provides high-availability, it also requires the least amount of bespoke support from the underlying infrastructure.

MQ Assets


TODO Uniform clusters (mqsc/ini)

All of the high-availability topologies in this deployment guide leverage the NativeHA feature of IBM MQ for resiliency. As the topologies grow more complex, additional configurations and deployments are added to this least-common architectural denominator.

The recently released NativeHA capability allows for multiple QueueManager pods to be running, with only one of them truly being "active" and receiving traffic from the OpenShift Route or Service. The running pods, managed by a StatefulSet on the underlying Kubernetes-based platform, actively share log and message data between the active and passive QueueManager instances. Once the active QueueManager instance becomes unavailable for any reason, the remaining passive pods take advantage of the RAFT algorithm to elect a new leader and within seconds failover to a different QueueManager instance, while minimizing service and message unavailability.

For more details on the early release of NativeHA for IBM MQ 9.2, you can check out the official IBM MQ Docs.

Our example here sets the following properties in the QueueManager YAML file and pushes the changes to your GitOps repo:

  type: NativeHA
      secretName: <inter-queuemanager-tls-cert-secret>
      cipherSpec: ANY_TLS12_OR_HIGHER
  defaultClass: ibmc-vpc-block-metro-10iops-tier
    enabled: true
    size: 2Gi
    type: persistent-claim
  • The availability.type setting is required to be NativeHA to take advantage of this capability.
  • The availability.tls setting allows for TLS-encrypted communication between QueueManager instances in the StatefulSet.
  • The storage.defaultClass setting should point to a multi-AZ supported storage class the provides ReadWriteOnce storage capability for Block Storage.
  • The storage.queueManager setting is required to be enabled and set to type persistent-claim for NativeHA fail-over capability to function.

Client Application Recommendations



Our sample client application is available under the Building MQ applications section. There are minimal additional configuration requirements to deploy the client application connected to this topology.

To be addressed:

  • Automatic client reconnection
  • Connects to a single Route URL provided by the MQ QueueManager instance
  • As only a single region is deployed, there is no consideration given for message sequencing needs beyond traditional single QueueManager requirements.