Maria Cluster Member Status Test

A MariaDB Cluster is built on multiple database nodes that work together using Galera synchronous replication. In this setup, each node can accept queries, and updates made on one node are immediately replicated to others to ensure consistency. Nodes can operate in primary or secondary roles, and their health directly affects the overall stability of the cluster. If a node goes into read-only mode, becomes unsynced, or gets disconnected, it can disrupt workload distribution, delay transactions, or even threaten data reliability. Issues such as nodes failing to sync, frequent role switches, uneven distribution of read/write nodes, or an increase in disconnected or joining nodes can all degrade cluster performance and availability.

This test tracks critical parameters like node roles, health state, number of synced/unsynced nodes, and the availability of read-write vs. read-only nodes. By doing so, it helps administrators detect early warnings, isolate failing nodes, and ensure that the MariaDB Cluster remains balanced, resilient, and performant.

Target of the test : A MariaDB Cluster

Agent deploying the test : An external agent

Outputs of the test : One set of results for each node on the MariaDB Cluster being monitored.

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed.
Host	The IP address of the MariaDB Cluster.
Port	The port on which the server is listening. By default, this is set to 3306.
Database	Specify the name of the database that is to be monitored on the target MariaDB Cluster.
User and Password	The eG agent has to be configured with the credentials of a user who has server-wide PROCESS and SELECT privileges on the monitored Maria Cluster Database server. To know how to create such a user, refer to Configuring the eG Agent with Access Privileges section.
Confirm Password	Confirm the Password (if any) by retyping it here.
SSL	This indicates that the eG agent will communicate with theMaria cluster via HTTPS or not. By default, this flag is set to No, as the target Maria database is not SSL-enabled by default. If the target cluster is SSL-enabled, then set this flag to Yes.
Verify CA	If the eG agent is required to establish an encrypted connection with the target MariaDB Cluster by authenticating the server's identity through verifying the server CA certificate, set Verify CA flag to Yes. By default, this flag is set to No.
Available Nodes	In the Available Nodes text box, provide a comma-separated list of all the available nodes to be included for monitoring. This way, the test monitor and collect metrics from all the available nodes in the cluster. By default, this parameter is set to none. The format of this configuration is: HOSTNAME:PORT, for example, 172.16.8.136:3306,172.16.8.139:3306
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test

Measurement

Description

Measurement Unit

Interpretation

Status

Indicates the current status of this cluster node.

This measure is not reported for the Summary descriptor.

The values reported by this measure and their numeric equivalents are available in the table below:

Measure Value	Numeric Value
MISSING OR REMOVED	0
WAITING	1
JOINING	2
DONOR	3
JOINED	4
SYNCED	5
NON-JOINED	6
INITIALIZED	7

Note:

This measure reports the Measure Values listed in the table above to indicate the status of this node. However, in the graph, this measure is indicated using the Numeric Values listed in the table above.

Is this primary node?

Indicates whether or not this node is the primary node in the cluster.

This measure is not reported for the Summary descriptor.

The values reported by this measure and their numeric equivalents are available in the table below:

Measure Value	Numeric Value
No	0
Yes	1

Note:

This measure reports the Measure Values listed in the table above to indicate whether/not the node is a primary node. However, in the graph, this measure is indicated using the Numeric Values listed in the table above.

Has the role of this node changed?

Indicates whether or not this node has switched roles (e.g., primary to secondary or vice versa).

This measure is not reported for the Summary descriptor.

The values reported by this measure and their numeric equivalents are available in the table below:

Measure Value	Numeric Value
No	0
Yes	1

Note:

This measure reports the Measure Values listed in the table above to indicate whether/not role of the node has switched. However, in the graph, this measure is indicated using the Numeric Values listed in the table above.

Use the detailed diagnosis of this measure to find out the Host, Current state, Previou state, Port, and Access mode.

Is this node in read-write mode?

Indicates whether or not this node is currently operating in read-write mode.

This measure is not reported for the Summary descriptor.

The values reported by this measure and their numeric equivalents are available in the table below:

Measure Value	Numeric Value
No	0
Yes	1

Note:

This measure reports the Measure Values listed in the table above to indicate whether/not the node is in read-write mode. However, in the graph, this measure is indicated using the Numeric Values listed in the table above.

Total number of nodes

Indicates the total number of nodes configured in the cluster.

Number