NDB data node status

Job details

Parameters

Job Summary

• Purpose: This job is aimed at checking the status of data nodes in NDB cluster database. It is specifically geared towards MySQL databases.
• Why: Regularly monitoring the status of data nodes in an NDB cluster database is crucial to prevent any form of database downtime or lag that could affect the performance of the overall system. This job particularly comes in handy in maintaining the health and performance of the database.
• Manual checking: To manually check the status of data nodes in an NDB cluster database, you can use the following SQL commands:

SELECT node_id, node_hostname FROM ndbinfo.config_nodes WHERE node_id NOT IN (SELECT node_id FROM ndbinfo.nodes) AND node_type='NDB';

Additional Information

• This job belongs to the ‘Cluster and Replication’ category and is set to execute every minute, as defined by its default schedule.
• The procedure used for this task is ‘dbw_ndb_data_node_status’ with a dependency on the same procedure and on a dependency table, ‘dbw_ndb_data_node_status_histr’.
• In the event of a failure, a cleanup process will be initiated that involves dropping the ‘dbw_ndb_data_node_status_histr’ table and the ‘dbw_ndb_data_node_status’ procedure.
• The job also comes with a reporting component that generates a report titled ‘NDB data node status’, with the report containing details such as node ID, hostname, and history date.
• The job implementation involves creating a table to store the history of data node status and a procedure that checks for any down nodes and updates the check values.

Dependencies

Cleanup Commands