Distributed Concurrency: How to actually stop a zombie write?
mrvladp · reddit · 2026-08-18
The post explores a common distributed concurrency failure where a delayed response from a timed-out worker overwrites data after the task was reassigned. The author analyzes the limitations of four mechanisms: locks (risk of deadlock), leases (expiration doesn't stop late writers), version checks (blind spots if data hasn't changed), and fences (verifying ownership grant). The proposed solution is a "generation" mechanism: increment a generation number on every ownership change and verify both generation and version atomically during commit. This approach mirrors concepts discussed by Martin Kleppmann.
More from Research
- Kimi K3 Kernel Achieves 2.05x Speedup Over Official FlashKDA — ChengleiSi · 2026-08-19
- Nature paper: Epigenetic drift in microglia drives aging — rand_longevity · 2026-08-19
- NeurIPS Competition SimulacraBench: AI Survey Prediction — soumitrashukla9 · 2026-08-19
- AI for Science: Estimating Bacteria Size with Code — johnowhitaker · 2026-08-19
- UAI 2026 paper: identifiability metrics show systematic false positives in interpretability evals — RexDouglass · 2026-08-19
- GenBio AI releases AIDO Cell preview: one world model simulating the whole human cell — AllThingsApx · 2026-08-19