Uber Redesigns M3DB Sharding with Subclusters to Limit Failure Impact
Uber has redesigned shard placement in M3DB with fixed size subclusters to limit the impact of node failures, maintenance, and cluster scaling. The approach bounds shard dependencies, preserves replica isolation, and uses a greedy algorithm to select shard migrations while avoiding a separate rebalancing pass and unnecessary data movement. By Leela Kumili
We haven't written up this one. InfoQ has the full story — the link below goes straight to it.
