← Founder Notes
Archive

Uber just rebuilt its metrics database sharding to bound failure blast radius. m3db now places…

Yethikrishna ROriginal on Threads

uber just rebuilt its metrics database sharding to bound failure blast radius. m3db now places shards in fixed-size subclusters, isolating replica groups and limiting the impact of a single node failure.

the fix is a scheduling problem, not a storage one.

Context

Uber Engineering's post of September 1, 2026, by Riya Tyagi, describes M3DB placing nodes into fixed-size subclusters, each owning a distinct non-overlapping slice of the shard space, with no shard shared across subclusters. Its example is 12 nodes at replication factor 3 with 6 nodes per subcluster, giving 2 subclusters. The baseline it describes is the sharded algorithm in which any node can own any shard, so one node failure can affect up to (n-1)/n of the cluster. Greedy shard donation keeps donor subclusters balanced when scaling.

How it compares

The post gives constraints: the isolation group count must match the replication factor, instancesPerSubcluster must be a multiple of the replication factor, scaling happens in multiples of the subcluster size, and AddReplica is not supported. Its conclusion states benefits qualitatively, and no measured production numbers were found in the passages read, nor the rollout scope at Uber. The sharded algorithm remains appropriate for smaller clusters per the post. The note gives no date, and rebuilt reads as a placement algorithm option and not a storage redesign. The fix is a scheduling problem is the author's take.

Watch next

  • Measured results and the M3DB release carrying the algorithm.

Sources

  1. Uber Engineering: From Chaos to Control (September 1, 2026)uber.com

Provenance

The note above is reproduced unedited from the original post, first published on Threads on 22 September 2026 at 15:49 IST. Sources are the papers and datasets the note draws on.

View the original post
Embed this note
<iframe src="https://founder.myndlabs.tech/notes/embed/uber-just-rebuilt-its-metrics-database-sharding-to-DdlgVkNCAmo" width="480" height="420" style="border:0;max-width:100%" loading="lazy" title="Uber just rebuilt its metrics database sharding to bound failure blast radius. m3db now places…"></iframe>

More notes