Fix Auto-scaling Issues

Alert Conditions

To trigger alerts, you can configure the following alert conditions in the project-level alert settings page.

• Auto-scaling: Compute auto-scaling initiated for base tier occurs if Atlas starts compute auto-scaling for any of the operational nodes in your dedicated cluster. Atlas can scale disk capacity as part of this event.

• Auto-scaling: Compute auto-scaling initiated for analytics tier occurs if Atlas starts compute auto-scaling for any of the analytics nodes in your dedicated cluster. Atlas can scale disk capacity as part of this event.

• Auto-scaling: Compute auto-scaling down didn't initiate for base tier due to storage requirements occurs if Atlas couldn't start compute auto-scaling for any of the operational nodes in your dedicated cluster as the configured storage size isn't supported by the target cluster tier.

• Auto-scaling: Compute auto-scaling down didn't initiate for analytics tier due to storage requirements occurs if Atlas couldn't start compute auto-scaling for any of the analytics nodes in your dedicated cluster as the configured storage size isn't supported by the target cluster tier.

• Auto-scaling: Compute auto-scaling didn't initiate for base tier due to maximum configured cluster tier occurs if Atlas couldn't scale up an operational node because your cluster reached a maximum cluster tier configured for auto-scaling.

• Auto-scaling: Compute auto-scaling didn't initiate for analytics tier due to maximum configured cluster tier occurs if Atlas couldn't scale up an analytics node because your cluster reached a maximum cluster tier configured for auto-scaling.

• Auto-scaling: Compute auto-scaling didn't initiate for base tier due to insufficient oplog size occurs if Atlas couldn't scale up an operational node due to insufficient oplog size. To learn more, see Set Minimum Oplog Window.

• Auto-scaling: Compute auto-scaling didn't initiate for analytics tier due to insufficient oplog size occurs if Atlas couldn't scale up an analytics node due to insufficient oplog size. To learn more, see Set Minimum Oplog Window.

• Auto-scaling: Disk auto-scaling initiated occurs when Atlas starts auto-scaling disk capacity.

• Auto-scaling: Disk auto-scaling didn't initiate due to the cluster reaching maximum available disk size occurs if Atlas couldn't scale up the disk size because the cluster has reached maximum available disk size.

• Auto-scaling: Disk auto-scaling didn't initiate due to insufficient oplog size occurs if Atlas couldn't scale up the disk size because the cluster's oplog size isn't sufficient. To learn more, see Set Minimum Oplog Window.

Common Triggers

Auto-scaling alerts occur by default for your cluster when Atlas triggers them. You can change who receives these alerts and their distribution. To learn more about how auto-scaling behaves, see Configure Auto-Scaling.

Automatic scaling might not occur when a cluster receives a burst of activity, such as a bulk insert. To reduce the risk of running out of resources during automatic scaling up events, monitor your cluster during bulk inserts and other workload spikes.

Fix the Immediate Problem

If your cluster nodes run out of memory or disk space, you can upgrade your cluster to fix the immediate problem. You can select a cluster tier with more memory, storage, and IOPS.

Monitor Your Progress

See Monitor cluster metrics.