Rule #2: Double Tap. An Elasticsearch Journey of Resiliency
summary
Chronicle of specific fixes: Elasticsearch adds a translog write‑ahead log so uncommitted writes replicate to replicas, reducing data loss; deploys anti-affinity rules so shards don’t all land on one host; implements circuit breakers that abort queries before JVM OOMs; and replaces manual quorum settings with Zen 2 (released in 7.0) after using TLA+ model checking to find consensus bugs. These changes are implemented and materially reduce split‑brain incidents and recoverability failures.
AI-written summary · about
chapters (5)
related talks
16mTop Elasticsearch tips
44mSurviving Elasticsearch
22mDesigning Concurrent Distributed Sequence Numbers ...
47mDatabase Resiliency
43mPartitions for Everyone!
46mTwo steps forward, one step backward - backward compatibility in Elasticsearch
41m(R)Evolution — You Know, for Search…
46mEdge Performance with In memory NoSQL
