# Atlas storage auto-scaling triggers, cooldowns and write blocking > Source-anchored research for Atlas storage auto-scaling triggers, cooldowns and write blocking. Run status: COMPLETED. Parent: [Oplog sizing under storage auto-scaling](https://llms-explorer.com/tree/oplog-sizing-under-storage-auto-scaling/) · 3 facets · 15 facts · page: https://llms-explorer.com/tree/atlas-storage-auto-scaling-triggers-cooldowns-and-write-blocking/ ## How it works - After disk auto-scaling triggers, subsequent automatic and manual disk scaling may be unavailable for a few hours. This general policy statement does not specify a universal fixed cooldown duration. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/cluster-autoscaling-storage.md) - Atlas may increase the cluster tier to accommodate disk growth even when cluster-tier scaling is disabled; storage growth can therefore alter compute capacity and cost. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/cluster-autoscaling-storage.md) - For Atlas Core, critically low free disk space on the primary blocks replica-set writes while reads continue. Deletes are blocked too because they can temporarily consume disk. Sharded clusters block writes routed to the affected shard. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md) - Crossplane provider-mongodbatlas issue 191 reported repeated DISK_SIZE_GB_TOO_SMALL failures when reconciliation reapplied initProvider.diskSizeGb after Atlas had auto-expanded the disk. The author traced it to Upjet TPF initProvider merging; the issue was closed as completed on 2026-10-21 after an Upjet update. (low confidence) (verified as of 2026-10-21) — [source](https://github.com/crossplane-contrib/provider-mongodbatlas/issues/191) ## Measurements and reference values - Atlas Core enables storage auto-scaling by default; 90% disk usage on any cluster node triggers expansion targeting 70% utilization on AWS, Azure and GCP. Storage does not automatically shrink. (medium confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/cluster-autoscaling-storage.md) - Documented free-space block/unblock thresholds are below 600 MiB/above 900 MiB for 8–20 GiB disks, below 4%/above 6% for 20 GiB–1.25 TiB disks, and below 50 GiB/above 75 GiB for disks at least 1.25 TiB. These are recovery hysteresis thresholds, separate from the 90% auto-scaling trigger. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md) ## Facts and statements - Auto-expansion can lose the race against rapid writes, including migration or bulk-insert bursts; capacity limits can also prevent expansion. Scale ahead of known bursts and monitor disk headroom. (high confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/cluster-autoscaling-storage.md) - Atlas Core delays auto-scaling until the oplog window covers the estimated scaling time. An enabled auto-scaling switch alone does not guarantee an immediate scale event. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/customize-storage.md) - Atlas automatically unblocks writes after free space recovers past the applicable recovery threshold. Increasing storage manually or enabling auto-expansion are documented recovery actions. (medium confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md) - Stacktape exposes disableDiskScaling separately from disableScaleDown in its MongoDbAutoScaling interface; the latter controls compute-tier downscaling. Treat the two flags as different configuration controls. (low confidence) (verified as of 2021-11-01) — [source](https://stacktape-docs.web.app/resources/mongo-db-atlas-clusters) - Storage auto-scaling only increases capacity; reducing storage requires a manual change. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/cluster-autoscaling-storage.md) - Different instance classes for base and analytics nodes disable disk auto-scaling. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/cluster-autoscaling-storage.md) - Write blocking applies to M10+ clusters running MongoDB 8.0 or later, despite the broader IWM overview describing MongoDB 9.0 eligibility. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md) - Blocked-write log reasons vary by FCV: 9.0+ uses InsufficientDiskSpace; earlier FCVs use DiskUseThresholdExceeded. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md) - Atlas provides default alerts for writes blocked by critically low storage and for writes subsequently unblocked; recovery occurs automatically after the unblocking threshold is crossed. (high confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/atlas/reference/alert-resolutions/disk-space-used.md)