InnoDB cluster switch
Job details
| Name: | InnoDB cluster switch |
| Platform: | Mysql |
| Category: | Cluster and Replication |
| Description: | NDB data node status |
| Long description: | |
| Version: | 1.7 |
| Default schedule: | 60s |
| Requires engine install: | No |
| Compatibility tag: | .[type=‘instance’ & is_mysql_branch=‘1′] |
Parameters
| Name | Default value | Description |
|---|---|---|
| return_status | 1 | Return status value (ALARM – 2, WARNING – 1, or OK – 0) when switch occurs (PRIMARY to SECONDARY or SECONDARY to PRIMARY). |
| keep_status | 10 | For how long (in minutes) the jobs status will be kept when switch occurs (PRIMARY to SECONDARY or SECONDARY to PRIMARY). |
Job Summary
- Purpose: The primary purpose of this job is to monitor if there is a switch case (either from PRIMARY to SECONDARY or from SECONDARY to PRIMARY) for the InnoDB cluster in a MySQL platform. This job is designed to pick up any changes and alert the necessary personnel as required.
- Why: This job is essential to ensure the smooth functioning of the MySQL. If there are unexpected changes in the PRIMARY/SECONDARY roles, it can have a significant impact on the load distribution and performance of the database system. Using this job, one can make sure any switches are picked up swiftly and dealt with aptly.
- Manual Checking: It does not provided detail regarding the SQL Commands for manual checking.
Technical Details
- Company: dbwatch.no
- Group: com.dbwatch.job
- Artifactid: mysql_innodb_cluster_switch
- Display-name: InnoDB cluster switch
- Description: This job checks if InnoDB cluster PRIMARY/SECONDARY switch occurs.
- Category: Cluster and Replication
- Default-schedule: 60s
- Entity Type: scheduledtask
Result
On executing this monitoring job, the following data is updated or recorded:
- Status: The status of the switch (either PRIMARY to SECONDARY or SECONDARY to PRIMARY).
- Details: More information about the switch.
- last_read_only_stat, last_super_read_only_stat, last_read_only_switch: These fields store the previous values which are compared with the current values to check if there any changes.
- last_innodb_switch_count: This field keeps track of the number of switches so far.
Report Template
The job also includes a report template which provides a detailed breakdown of an InnoDB cluster PRIMARY/SECONDARY switch. The report includes:
- Version: 2
- Title: PRIMARY/SECONDARY switch
- Description: PRIMARY/SECONDARY switch.
- Default-schedule: 0 * * *
- Text: InnoDB cluster PRIMARY/SECONDARY switch
It covers a presentation with details and is designed to extract data about “Details” and present it in a table format.