Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

Support Policies for RHEL High Availability Clusters - corosync-qdevice and corosync-qnetd

Updated on

Request a new translation or translation update

A translation for your language preference does not exist. Click below to request a translation for your selected language.

Submit request

Contents

Overview

Applicable Environments

  • Red Hat Enterprise Linux (RHEL) with the High Availability Add-On
  • Cluster architectures involving a quorum device provided through qdevice and qnetd

Useful References and Guides

Introduction

This policy guide explains Red Hat's requirements and support limitations regarding quorum devices using corosync-device and corosync-qnetd in a RHEL High Availability cluster.

Policies

Available/Supported Releases:

  • RHEL 8, 9, 10: corosync-qdevice and corosync-qnetd are supported by Red Hat
  • RHEL 7: corosync-qdevice and corosync-qnetd are supported technologies as of RHEL 7.4 - using releases corosync-qdevice-2.4.0-9.el7 and corosync-qnetd-2.4.0-9.el7 or later.
    • NOTE: qdevice and qnetd are available for usage in RHEL High Availability clusters starting with RHEL 7 Update 3, but are considered a Technology Preview in that release.

Supported Cross Architecture & Cross Version corosync-qdevice and corosync-qnetd:

  • There is no support for mixing architecture when using corosync-qnetd and corosync-qdevice. The architecture of the host runningcorosync-qnetd and cluster nodes that using corosync-qdevicehas to be the same.
  • Mixing of RHEL versions using corosync-qnetd and corosync-qdevice
    • Supported mixing of RHEL versions using corosync-qnetd and corosync-qdevice
      • It is supported to mix of RHEL 7 qdevice and RHEL 8 qnetd or vice versa RHEL 8 qdevice and RHEL 7 qnetd: supported.
        • EXAMPLE: Our cluster is based on RHEL 8 but we would like to use our RHEL 7 arbiter (qnetd). This is possible and supported.
        • EXAMPLE: Our cluster is based on RHEL 7 but we would like to introduce an arbiter (qnetd) on RHEL 8. This is possible and supported.
    • Unsupported mixing of RHEL versions using corosync-qnetd and corosync-qdevice
      • There is no support for mixing of RHEL 9 or later with any other RHEL release for corosync-qdevice and corosync-qnetd.
        • EXAMPLE: Our cluster is based on RHEL 9 but we would like to use our RHEL 10 arbiter (qnetd). This is not supported.
        • EXAMPLE: Our cluster is based on RHEL 8 but we would like to introduce an arbiter (qnetd) on RHEL 10. This is not supported.

A JIRA was opened to explore what combinations of RHEL versions of corosync-qnetd and `corosync-qdevice are supported in combination:


Mixing Bare Metal and Virtual Platforms

  • It is possible and supported to use a virtual machine qnetd server with a cluster made up of bare metal members or members on a different virtualization platform.
  • It is possible and supported to use a bare metal qnetd server with a cluster made up of virtual machine members.
  • All support policies related to the cluster members' platforms still apply.

Number of Quorum Devices / Servers: A cluster may only utilize a single qdevice interacting with a single qnetd quorum server.


Number of Clusters per Quorum Device / Server: Multiple clusters may utilize the same qnetd quorum server. There is no hard limit set for maximum number of clusters that can connect to qnetd (corosync-qnetd) by default.


Managing qnetd in a High Availability Cluster: It is supported to use the corosync-qnetd resource agent in a RHEL High Availability Cluster to make qnetd highly available (although usually not necessary as a cluster with a qnetd arbiter will work if only the qnetd device goes offline).  It is not supported for a cluster to manage it's own qnetd arbiter.


Quorum device heuristics: corosync-qdevice provides functionality that allows an administrator to configure "heuristics" that evaluate true or false and influence the scoring algorithm of qdevice. This functionality is subject to the following conditions:


Additional information

The quorum device (package corosync-qnetd) should never be installed in one of the cluster nodes, it has to be hosted in a system aside. Hosting it in one of the cluster nodes is not supported.

This solution is part of Red Hat's fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Red Hat LinkedIn YouTube Facebook X, formerly Twitter

Quick Links

Help

Site Info

Related Sites

© 2026 Red Hat