Replica count
Job details
| Name: | Replica count |
| Platform: | Mysql |
| Category: | Cluster and Replication |
| Description: | NDB data node status |
| Long description: | |
| Version: | 1.5 |
| Default schedule: | 60s |
| Requires engine install: | No |
| Compatibility tag: | .[type=‘instance’ & databasetype=‘mysql’]/instance[is_mysql_branch=‘1′] |
Parameters
| Name | Default value | Description |
|---|---|---|
| min_slave_hosts | 0 | The minimum number of slave hosts (replicas) registered with the source host. |
| return_status | 1 | Return status value (ALARM – 2, WARNING – 1, or OK – 0) when the number of slave hosts (replicas) registered with the source is less than min_slave_hosts parameter value. |
Job Summary
- Purpose: The primary purpose of this job, titled “Replica count”, is to monitor and check all replicas currently registered with the MySQL database’s source host.
- Why: This job is crucial for maintaining database replication, which ensures that data is continuously copied and updated from one database (source) to another (replica). It allows a real-time accurate count of replicas connected to the source host, offering alarms or warnings when the number of registered slave hosts is less than minimum set value.
- Manual checking: Manual verification of this function can be done by checking the replica count on the MySQL instance.
Check with the "SHOW SLAVE HOSTS" MySQL command, it will display the list of all registered slave hosts.Job Details
- The job employs an XML content structure and runs on a JavaScript engine.
- This job is part of the “Cluster and Replication” category, it is periodically scheduled to run every 60 seconds to ensure real-time monitoring and tracking.
- This job has “ALARM“, “WARNING“, and “OK” return status to signify the state of replica counts compared to the minimum threshold.
- It primarily functions on the basis of two parameters:
- The minimum number of slave hosts required, represented by the “min_slave_hosts” parameter.
- The return status value when the real-time number is lesser, represented by the “return_status” parameter.
Job Reports
- The job includes a detailed report presentation labeled “Replica count”.
- The report gives an overview of the status between the replication SQL (applier) thread and the replication I/O (receiver) thread.
- It contains a well-structured table providing pertinent details regarding replicas and their current status.
- The report is scheduled to run every minute.
Developed By
This job was developed by dbwatch.no with a version number of 1.5.
The unique identifier for the job is “mysql_replica_count” under the group “com.dbwatch.job”.