MySQL Cluster Process Test
This test reports the total number of processes executing on the target MySQL database cluster and the number of processes in the different process states - starting, running, stopping, stopped, failed, unknown etc. Using this test, administrators can isolate failed processes and can initiate a probe to figure out the reason behind the failed processes.
Target of the test : A MySQL Cluster
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each node in the target cluster being monitored
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The host for which the test is to be configured. |
Port |
The port at which the specified host listens. |
MCMPath |
Specify the full path to the location where the target MySQL Cluster manager is installed. For example, your location can be C:\Users\user\AppData\Roaming/mcmd.conf. By default, none is specified against this parameter. |
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:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Process count |
Indicates the total number of processes executing on this node. |
Number |
This measure is a good indicator of process load on each node of the target MySQL database cluster. |
Added processes |
Indicates the number of processes that were added to this node during the last measurement period. |
Number |
The detailed diagnosis of this measure lists the name of the processes/package executing the processes that were added for each node. |
Starting processes |
Indicates the number of processes that were in Stating state during the last measurement period. |
Number |
The detailed diagnosis of this measure lists the name of the processes/package executing the processes that were in Starting state for each node. |
Running processes |
Indicates the number of processes that were in Running state during the last measurement period. |
Number |
The detailed diagnosis of this measure lists the name of the processes/package executing the processes that were in Running state for each node. |
Stopping processes |
Indicates the number of processes that were in Stopping state during the last measurement period. |
Number |
The detailed diagnosis of this measure lists the name of the processes/package executing the processes that were in Stopping state for each node. |
Stopped processes |
Indicates the number of processes that were stopped on this node during the last measurement period. |
Number |
The detailed diagnosis of this measure lists the name of the processes/package executing the processes that were in Stopped state for each node. |
Failed processes |
Indicates the number of processes that failed on this node during the last measurement period. |
Number |
Ideally, the value of this measure should be 0. The detailed diagnosis of this measure lists the name of the processes/package executing the processes that failed for each node. |
Unknown processes |
Indicates the number of processes that were in an Unknown state during the last measurement period. |
Number |
The detailed diagnosis of this measure lists the name of the processes/package executing the processes that were in Unknown state for each node. |