This article details a production Flink CDC server_id conflict caused by copied configurations, explaining how to identify duplicate server_id/server_uuid via MySQL SHOW PROCESSLIST, assign unique identifiers, clear Flink checkpoint state, and verify resolution through logs and replication monitoring.
The article analyzes a MySQL cascade replication issue where the new slave failed to sync due to duplicate server_id values, explains the root cause stemming from automated server_id assignment, and provides step‑by‑step remediation to ensure unique server_id settings and reliable replication.
This article explains a MySQL replication experiment where a master is restored from an outdated backup, leading to missing GTID transactions due to server_id filtering, and provides analysis and solutions such as changing server_id or enabling replicate-same-server-id to prevent data loss.
This article explains how duplicate MySQL server_id or server_uuid values in replication topologies can cause data loss during high‑availability failover, illustrates the underlying mechanisms with diagrams, and provides practical configuration recommendations to avoid these issues.
