# Reducing shard count and unsharding collections on Atlas > Source-anchored research for Reducing shard count and unsharding collections on Atlas. Run status: COMPLETED. Parent: [Shard Key Design and Resharding as Cost Levers](https://llms-explorer.com/tree/shard-key-design-and-resharding-as-cost-levers/) · 5 facets · 11 facts · page: https://llms-explorer.com/tree/reducing-shard-count-and-unsharding-collections-on-atlas/ ## Structure and components - Treat cost reduction as a configuration comparison, not a fixed savings percentage: Atlas previews configuration pricing excluding data transfer, and each Atlas Core shard consists of replica-set data-bearing servers. (low confidence) (verified as of 2026-10-30) — [source](https://www.mongodb.com/docs/atlas/scale-cluster.md) ## How-to and procedures - Check collection-level balancing as well as global balancer state: SERVER-113851 reports MongoDB 7.0.26 removal hanging after sh.disableBalancing on some collections. This report alone does not establish an Atlas defect or a current-version regression. (low confidence) — [source](https://jira.mongodb.org/browse/SERVER-113851) ## Problems, failure modes and limitations - Atlas supports reducing a sharded cluster to one shard, but its documentation says replica-set-to-sharded conversion cannot be reversed; consolidation therefore does not by itself restore replica-set topology. (high confidence) (verified as of 2026-10-30) — [source](https://www.mongodb.com/docs/atlas/scale-cluster.md) - Destination storage capacity is a consolidation prerequisite. Percona identified insufficient space on remaining shards as a removal caveat in its March 2021 operator design; this corroborates a planning risk, not an Atlas automation guarantee. (low confidence) — [source](https://www.percona.com/blog/a-peek-at-percona-kubernetes-operator-for-percona-server-for-mongodb-new-features/) ## Comparisons and alternatives - The balancer must be enabled to drain sharded data; a disabled balancer prevents shard removal from completing. Shard reduction is asynchronous migration rather than immediate infrastructure deletion. (high confidence) (verified as of 2026-10-30) — [source](https://www.mongodb.com/docs/atlas/scale-cluster.md) - Alibaba Cloud documents that short balancer windows prolong shard removal and that migration adds workload. Treat a wider window as a throughput-versus-service-load tradeoff; its provider-specific tuning instructions do not establish Atlas-supported controls. (low confidence) (verified as of 2026-08-20) — [source](https://www.alibabacloud.com/help/en/mongodb/use-cases/confirm-the-progress-of-adding-or-removing-shard-nodes) ## Facts and statements - Atlas removes shards in descending order of the number in their _id field; for shard0, shard1 and shard2, reducing to two removes shard2. Other configuration changes wait for shard removal to finish. (high confidence) (verified as of 2026-10-30) — [source](https://www.mongodb.com/docs/atlas/scale-cluster.md) - Reduce shard count through Atlas cluster configuration; the self-managed removeShard command is explicitly unsupported in Atlas. (high confidence) (verified as of 2026-10-30) — [source](https://www.mongodb.com/docs/atlas/scale-cluster.md) - Atlas documents sharded collections as remaining online during removal; in MongoDB 8.0 it uses moveCollection for eligible unsharded collections, but its fallback to offline movePrimary prevents a blanket zero-downtime guarantee. (high confidence) (verified as of 2026-10-30) — [source](https://www.mongodb.com/docs/atlas/scale-cluster.md) - Jumbo chunks can strand a shard in draining state. Percona illustrates removal stuck with three remaining jumbo chunks, and Alibaba documents jumbo chunks blocking removal. These are operational MongoDB findings, not Atlas-specific incident evidence. (high confidence) — [source](https://www.percona.com/blog/dealing-with-jumbo-chunks-in-mongodb/) - Shard removal can close change-stream cursors that may not be fully resumable, according to the server command reference; assess consumer recovery separately from collection availability. (low confidence) (verified as of 2026-10-30) — [source](https://www.mongodb.com/docs/manual/reference/command/removeshard/)