Support Policies for RHEL High Availability Clusters - Management of a mariadb/mysql Database Server in a Cluster

Updated -



Applicable Environments

  • Red Hat Enterprise Linux (RHEL) with the High Availability Add-On

Useful References and Guides


This guide offers Red Hat's policies and requirement around the management of mariadb or mysql databases by a RHEL High Availability cluster.


mariadb/mysql releases and Red Hat resource-agents: Red Hat's mariadb/mysql resource-agents are developed with a target of managing the releases of this database server that are shipped as part of RHEL. Red Hat supports the mariadb agent when used in conjunction with mariadb / mysql releases shipped in that same release of RHEL as the cluster software that is being used.

Using non-RHEL mariadb/mysql releases: While Red Hat's agents may work with other non-RHEL mariadb/mysql releases, Red Hat cannot guarantee the behavior will be as expected, and does not test these combinations. It is up to the organization deploying any such combination to thoroughly test the operation of the agent being used and determine if it is adequate for that deployment's needs. In cases where Red Hat's mariadb or mysql resource agent is being used with a release of the database server other than what is shipped in that release of RHEL, Red Hat Support may be unable to assist with concerns relating to the agent's management of that release.

Using 3rd party or custom agents or scripts: In situations where Red Hat's agent is not adequate for managing the mariadb/mysql server(s) deployed on a cluster, customer organizations may wish to develop their own scripts or agents, or some 3rd party may offer a script or agent for this purpose. Red Hat's typical policy on 3rd-party or custom agents or scripts applies here.