Enhance Data Integrity with Binlog Event Checksum Verification

[why-arong]

Overview

This PR add supports for verifying event checksums when the binlog_checksum option is enabled in MySQL/MariaDB(5.7, 8.0). It enhances data integrity and security by validating each event in the binary log.

Changes

Key updates in this PR include:

• Introduction of the _verify_event method in the BinlogEvent class. When both the binlog_checksum option of MySQL/MariaDB and the verify_checksum option of BinLogStreamReader are active, this function:
  • Reads data, omitting the final CRC32 4 bytes.
  • Applies the zlib CRC32 algorithm on the data, then contrasts the outcome with the last 4 CRC32 bytes.
  • Restores the packet's state to its original condition post-execution.

The reason this method is effective lies in the shared use of the CRC32 algorithm by both MySQL and this method.

Test Code

To ensure the accuracy of the _verify_event method, test code has been designed to handle two main scenarios: valid events and corrupted events. The respective tests can be accessed in this source code file.

Benefits

• Enhances data integrity by verifying event checksums.
• Improves system reliability and reduces the risk of data loss.

Comment

Slave already has these features. When slave_sql_verify_checksum is enabled, the replication SQL thread uses checksums read from relay logs to verify data. I believe that incorporating these functionalities into our project would be highly advantageous.

[julien-duponchelle]

That's great !