# uber m3db subcluster sharding

Published articles for uber m3db subcluster sharding.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Uber Redesigns M3DB Sharding with Subclusters to Limit Failure Impact

DevFeed: [Uber Redesigns M3DB Sharding with Subclusters to Limit Failure Impact](<https://devfeed.tech/articles/uber-redesigns-m3db-sharding-with-subclusters-to-limit-failure-impact-57620.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/09/uber-m3db-subcluster-sharding/>)

Author: Leela Kumili

Published: 2026-09-21T14:37:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [sharding](<https://devfeed.tech/topics/sharding.md>), [Database](<https://devfeed.tech/topics/database.md>), [Replication](<https://devfeed.tech/topics/replication.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [Algorithms](<https://devfeed.tech/topics/algorithms.md>)

Tags: [algorithm](<https://devfeed.tech/tags/algorithm.md>), [algorithms](<https://devfeed.tech/tags/algorithms.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [availability](<https://devfeed.tech/tags/availability.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [data-movement](<https://devfeed.tech/tags/data-movement.md>), [database](<https://devfeed.tech/tags/database.md>), [database-replication](<https://devfeed.tech/tags/database-replication.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [fault-tolerance](<https://devfeed.tech/tags/fault-tolerance.md>), [load-balancing](<https://devfeed.tech/tags/load-balancing.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [migrations](<https://devfeed.tech/tags/migrations.md>), [news](<https://devfeed.tech/tags/news.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [replication](<https://devfeed.tech/tags/replication.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [sharding](<https://devfeed.tech/tags/sharding.md>), [time-series-data](<https://devfeed.tech/tags/time-series-data.md>), [uber](<https://devfeed.tech/tags/uber.md>), [uber-m3db-subcluster-sharding](<https://devfeed.tech/tags/uber-m3db-subcluster-sharding.md>)

### AI overview

Uber redesigned shard placement in its M3DB distributed time series database by introducing fixed-size subclusters. The design limits the effects of node failures, maintenance, and cluster scaling while preserving replica isolation. A greedy algorithm selects shard migrations to balance load and avoid unnecessary rebalancing and data movement.

### Source excerpt

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