0 views collected around this technical thread.
An in‑depth postmortem of a costly MySQL data‑migration failure caused by using INSERT INTO SELECT without proper indexing, detailing the OOM issue, full‑table scans, lock contention, and best practices to safely employ the statement.
The article explains that while MySQL foreign keys ensure data consistency and integrity, they introduce performance overhead, lock contention, and scalability issues—especially in high‑concurrency and sharded environments—leading many large internet firms to forego them in favor of application‑level solutions.
The article details how Didi’s large‑scale Ceph deployment suffered from high tail latency due to long‑held and coarse‑grained locks, and describes a series of fixes—including asynchronous read threads, fine‑grained object caches, per‑thread lock‑free logging, and lock‑free filestore apply—that cut latency by up to 90 % and more than doubled read throughput.
This article outlines a systematic approach to diagnosing and resolving DDL execution hangs in Dble, covering log inspection, context analysis, identifying problematic data nodes and MySQL connections, and confirming lock contention as the root cause.
The article investigates intermittent slow update performance in a Tencent Cloud internal system caused by massive lock_wait_thread contention, analyzes the underlying InnoDB lock mechanisms and thread behavior, implements a fix by disabling lock_wait_suspend_thread triggers, and demonstrates substantial latency reduction through benchmark results.
An in‑depth investigation reveals that when MySQL semi‑sync replication is configured with rpl_semi_sync_master_wait_for_slave_count=1, starting a second slave can cause the master’s dump thread to fail, leading to slave_io_thread stalls; the analysis includes reproduction steps, status checks, thread stack traces, and a patch using sched_yield to resolve the lock contention.