Support Policies for RHEL High Availability Clusters - corosync-qdevice and corosync-qnetd
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.
Contents
Overview
Applicable Environments
- Red Hat Enterprise Linux (RHEL) with the High Availability Add-On
- Cluster architectures involving a quorum device provided through
qdeviceandqnetd
Useful References and Guides
- Support Policies for RHEL High Availability Clusters
- RHEL High Availability Reference Guide - Quorum Devices
- Explore components:
corosync-qdeviceandcorosync-qnetd - Design Guidance for RHEL High Availability Clusters - Considerations with qdevice Quorum Arbitration
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-qdeviceandcorosync-qnetdare supported by Red Hat - RHEL 7:
corosync-qdeviceandcorosync-qnetdare supported technologies as of RHEL 7.4 - using releasescorosync-qdevice-2.4.0-9.el7andcorosync-qnetd-2.4.0-9.el7or later.- NOTE:
qdeviceandqnetdare available for usage in RHEL High Availability clusters starting with RHEL 7 Update 3, but are considered a Technology Preview in that release.
- NOTE:
Supported Cross Architecture & Cross Version corosync-qdevice and corosync-qnetd:
- There is no support for mixing architecture when using
corosync-qnetdandcorosync-qdevice. The architecture of the host runningcorosync-qnetdand cluster nodes that usingcorosync-qdevicehas to be the same. - Mixing of RHEL versions using
corosync-qnetdandcorosync-qdevice- Supported mixing of RHEL versions using
corosync-qnetdandcorosync-qdevice- It is supported to mix of RHEL 7
qdeviceand RHEL 8qnetdor vice versa RHEL 8qdeviceand RHEL 7qnetd: 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.
- EXAMPLE: Our cluster is based on RHEL 8 but we would like to use our RHEL 7 arbiter (
- It is supported to mix of RHEL 7
- Unsupported mixing of RHEL versions using
corosync-qnetdandcorosync-qdevice- There is no support for mixing of RHEL 9 or later with any other RHEL release for
corosync-qdeviceandcorosync-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.
- EXAMPLE: Our cluster is based on RHEL 9 but we would like to use our RHEL 10 arbiter (
- There is no support for mixing of RHEL 9 or later with any other RHEL release for
- Supported mixing of RHEL versions using
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
qnetdserver 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
qnetdserver 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:
- RHEL 10: Heuristics functionality is provided as a Technology Preview. An issue was opened to evaluate the possibility of full support: [RHEL-169175] evaluation of quorum device heuristics support in RHEL9/10.
- RHEL 9: Heuristics functionality is provided as a Technology Preview. An issue was opened to evaluate the possibility of full support: [RHEL-169175] evaluation of quorum device heuristics support in RHEL9/10.
- RHEL 8: Heuristics functionality is provided as a Technology Preview.
- RHEL 7: Heuristics functionality is provided as a Technology Preview in RHEL 7.7 and 7.6. This functionality was not available in earlier releases of RHEL 7.
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.