https://ahmetb.github.io/etcd-lsm/Recent content on Porting etcd to PebbleHugoen-usTue, 12 May 2026 00:00:00 +0000https://ahmetb.github.io/etcd-lsm/posts/06-what-were-not-doing/Tue, 12 May 2026 00:00:00 +0000https://ahmetb.github.io/etcd-lsm/posts/06-what-were-not-doing/Big migrations succeed by what they refuse to take on. A list of things this milestone deliberately punts — and why each refusal earns its keep.https://ahmetb.github.io/etcd-lsm/posts/04-disabling-pebbles-wal/Mon, 11 May 2026 00:00:00 +0000https://ahmetb.github.io/etcd-lsm/posts/04-disabling-pebbles-wal/etcd already has a Raft write-ahead log. Running Pebble’s WAL on top is wasted fsyncs. The trade-off is that we have to be exactly right about a single integer.https://ahmetb.github.io/etcd-lsm/posts/05-what-the-chaos-gate-surfaced/Mon, 11 May 2026 00:00:00 +0000https://ahmetb.github.io/etcd-lsm/posts/05-what-the-chaos-gate-surfaced/We ran the kill -9 gate. It surfaced three bugs in code we hadn’t touched. Two were structural; one cascaded from another.https://ahmetb.github.io/etcd-lsm/posts/03-bbolt-vs-pebble/Sun, 10 May 2026 00:00:00 +0000https://ahmetb.github.io/etcd-lsm/posts/03-bbolt-vs-pebble/A short primer on B+ trees and LSM-trees, and why the difference between them shows up at exactly the operational seams etcd operators care about.https://ahmetb.github.io/etcd-lsm/posts/02-sealing-the-bbolt-leaks/Sat, 09 May 2026 00:00:00 +0000https://ahmetb.github.io/etcd-lsm/posts/02-sealing-the-bbolt-leaks/Before any Pebble code can land, four bbolt-typed APIs have to leave the public Backend interface. Boring work, load-bearing outcome.https://ahmetb.github.io/etcd-lsm/posts/01-the-case-for-a-second-engine/Fri, 08 May 2026 00:00:00 +0000https://ahmetb.github.io/etcd-lsm/posts/01-the-case-for-a-second-engine/Why etcd is getting a Pebble (LSM-tree) backend alongside bbolt — what hurts at Kubernetes scale, and what we explicitly are not changing.