Speculative Recovery: Cheap, Highly Available Fault Tolerance with Disaggregated...
summary
Speculative recovery claims to cut REDS failover time by running failure detection and recovery in parallel using two new primitives super and collapse, implemented as a fast co‑located copy‑on‑write clone in a prototype called specReds. Evaluation on Docker+NVMe with MySQL/Postgres/MariaDB shows existing clone implementations raise write latency ~30×, while the co‑located clone matches regular disk performance and lets recovery race the primary. In a false‑positive test (primary returns after 10s, typical timeout 5s causing a 1‑minute recovery), speculative recovery aborts unnecessary failovers and significantly reduces outage time.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:26A nascent fault-tolerance technique
- 11:33super uses copy-on-write
- 12:32collapse uses a dirty bit to monitor writes
- 13:17Three components of a speculative recovery system
- 14:15The experiment setup
- 15:11Application recovery latency from various disk states
related talks
01h 12mRedundancy does not imply fault tolerance
18mWho's Afraid of Uncorrectable Bit Errors? Online Recovery of Flash Errors with Distributed Redundancy
24mPLOVER: Fast, Multi-core Scalable Virtual Machine Fault-tolerance
46mFault tolerance in Distributed Systems: A Case Study in Apache Spark
19mProtocol-Aware Recovery for Consensus-Based Storage
16mPilot Execution: Simulating Failure Recovery In Situ for Production Distributed Systems
35mMaking Ceph Fast in the Face of Failure
06mNobody Knows What PGs are Good For, Only I Do
