Monitoring MySQL Cluster

eG Enterprise provides an exclusive MySQL Cluster monitoring model that runs quick health checks on the MySQL Cluster at configured intervals, and proactively alerts administrators to potential bottlenecks to the performance of the server.

Figure 1 : The layer model of the MySQL Cluster Component

Using the model depicted by Figure 1, administrators can determine the following:

  • Is the MySQL Cluster database server running? If so, how many primary and secondary nodes are connected to the cluster?

  • Are the nodes in the target MySQL Cluster available? If so, how quickly does each node respond to user requests? How many nodes are unresponsive/unreachable?

  • Is the node overloaded?

  • Are clients able to connect to the node in the cluster, or are there too many connection failures?

  • Are connections been closed properly? Are there an unusual number of open connections to the node?

  • Is query execution efficient, or do queries need to be optimized for better performance?

  • Are there too many transactions experiencing errors on the nodes?

  • Is the replication time lag abnormally high?

This section will deal with the first layer of the layer model only, as the Network Layer have been discussed elaborately in the Monitoring Unix and Windows Servers document.