# Maintenance Impact Minimization > Depth-first rabbithole dossier for Maintenance Impact Minimization; source-anchored research pack. Parent: [Atlas Maintenance Windows](https://llms-explorer.com/tree/atlas-maintenance-windows/) · 3 facets · 5 facts · page: https://llms-explorer.com/tree/maintenance-impact-minimization/ ## How it works - [medium] When transitioning to a new cloud provider, deployment IP addresses change, and if you have low Disk IOPS, your cluster could experience brief performance degradation during maintenance while MongoDB repopulates the WiredTiger cache. Sources: https://www.mongodb.com/docs/atlas/tutorial/cluster-maintenance-window.md, https://www.mongodb.com/docs/atlas/reference/faq/deployment.md — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/maintenance-impact-minimization-a8096d69a3/rabbithole-synthesis.md#troubleshooting` ## Comparisons and alternatives - [low] Unlike self-managed deployments, Atlas triggers replica set elections during routine maintenance operations, which can impact data durability for non-majority write concerns. Sources: https://www.mongodb.com/docs/atlas/replica-set-rollbacks.md — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/maintenance-impact-minimization-a8096d69a3/rabbithole-synthesis.md#core` - [low] On Atlas Infinite clusters, the primary node can change during OS or VM maintenance, vertical scaling, MongoDB version upgrades and failures. The storage layer coordinates failover instead of an election, and a standby compute node becomes primary without oplog replay or a cold start. Sources: https://www.mongodb.com/docs/atlas/tutorial/test-resilience/test-primary-failover.md — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/maintenance-impact-minimization-a8096d69a3/rabbithole-synthesis.md#core` ## Facts and statements - [high] Atlas maintenance operations, including OS patches and MongoDB database maintenance patches, require at least one replica set election per replica set during the maintenance window. Sources: https://www.mongodb.com/docs/atlas/tutorial/cluster-maintenance-window.md, https://www.mongodb.com/docs/atlas/cli/current/command/atlas-api-maintenanceWindows-updateMaintenanceWindow.md, https://www.mongodb.com/docs/atlas/reference/faq/deployment.md, https://www.pulumi.com/registry/packages/mongodbatlas/api-docs/maintenancewindow/ — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/maintenance-impact-minimization-a8096d69a3/rabbithole-synthesis.md#core` - [low] Atlas performs maintenance operations on a rolling basis to avoid downtime, but each election creates a period where write concern `{ w: 1 }` writes may not have replicated to secondaries. Sources: https://www.mongodb.com/docs/atlas/replica-set-rollbacks.md — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/maintenance-impact-minimization-a8096d69a3/rabbithole-synthesis.md#core` ## Related concepts - Maintenance — is a part of Maintenance Impact Minimization - Impact — is a part of Maintenance Impact Minimization