1 views collected around this technical thread.
This article analyzes a MySQL master‑slave replication failure where the SQL thread stopped with error 1594, detailing log inspection, CRC checks, relay‑log corruption, root‑cause identification, and step‑by‑step remediation procedures for restoring replication.
This article explains a MySQL master‑slave synchronization failure caused by a corrupted relay log, walks through the replication principles, analyzes slave status and GTID differences, and provides step‑by‑step commands to skip the problematic GTID and restore replication.
This article analyzes how MySQL slave crashes can cause inconsistencies between master info and relay log positions during sync_master_info and sync_relay_log_info processes, presents case studies of duplicated events, explains the impact of different storage repositories (FILE vs TABLE), and recommends configuration settings to achieve server‑crash‑safe replication.
This article examines how slave crashes in MySQL replication can cause inconsistencies between master info and relay log positions, leading to duplicate events and errors such as 1062 and 1032, analyzes underlying mechanisms, presents case studies, and proposes configuration settings to achieve server‑crash‑safe replication.
The article analyzes a MySQL replication issue where a low slave_net_timeout combined with a larger MASTER_HEARTBEAT_PERIOD causes frequent zombie dump threads, leading to massive small relay‑log files, and provides detailed explanations, code references, and step‑by‑step remediation procedures.
This article explains the structure and purpose of the MySQL slave_relay_log_info table, how relay log positions are persisted and synchronized, the role of master_auto_position and GTID, and the mechanisms of relay_log_recovery to ensure reliable replication after crashes.
The article examines MySQL 5.6’s crash‑safe slave replication, explaining how earlier versions’ unsafe relay‑log handling could corrupt position data, describing the atomic update of mysql.slave_relay_log_info via table‑based relay‑log info and transaction coordination, and covering configuration options, recovery behavior, GTID implications, performance trade‑offs, and implementation guidance.