You can set the hour of the day when Atlas should start weekly maintenance on your cluster. This setting is optional and is not required for most clusters. Configure maintenance windows from your project settings.
Typically, you do not need to manually configure a maintenance window. Atlas performs maintenance automatically in a rolling manner to preserve continuous availability for resilient applications. You can use the Test Failover capability to ensure that your application is resilient to replica set elections.
Configuring maintenance windows provides more control over the timing of maintenance by allowing maintenance that requires replica set elections to occur at your preferred time of day, and other standard updates to occur outside of business-critical hours.
Maintenance Window Considerations
Urgent Maintenance Activities
Atlas may perform urgent maintenance activities (such as security patches for zero-day vulnerabilities) as soon as necessary without regard to configured maintenance windows or protected hours.
Ongoing Maintenance Operations
Once you schedule a maintenance window for your cluster, you cannot change it until any ongoing maintenance operations have completed.
MongoDB Database Upgrades
If maintenance includes a MongoDB patch version upgrade, Atlas displays the current and target versions in the console.
Maintenance Requires Replica Set Elections
Atlas performs maintenance the same way as the maintenance procedure described in the MongoDB Manual. This procedure requires at least one replica set election during the maintenance window per replica set.
Use the Test Failover capability to ensure that your application is resilient to replica set elections.
Maintenance Starts As Close to the Start of the Window As Possible
Maintenance always begins as close to the scheduled time as possible, but in-progress cluster updates or unexpected system issues could delay the start time.
Potential for Brief Performance Degradation during Maintenance
If you have low Disk IOPS, your cluster could experience a brief performance degradation during maintenance while MongoDB repopulates the WiredTiger storage engine. See Journaling and the WiredTiger Storage Engine to learn more.
Track Maintenance Completion
You'll see a Maintenance window completed event in your Project Activity Feed when maintenance operations finish.
Protected Hours Considerations
In addition to configuring a maintenance window, you can set daily protected hours, which is a window of time during which Atlas avoids performing standard updates.
Maintenance vs. Standard Updates
Atlas automatically performs maintenance during the maintenance window. However, Atlas may perform standard updates that do not involve a cluster restart or impact workload performance, outside of the maintenance window. When you enable protected hours, Atlas performs standard updates outside of the protected hours window.
Protected Hours Range
The length of your protected hours window cannot exceed 18 hours.
Required Access
To manage maintenance windows, you must have
Organization Owner or Project Owner access
to the project.
Procedure
Open Your Project Settings
In Atlas, go to the Project Settings page.
If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it's not already displayed, select your desired project from the Projects menu in the navigation bar.
In the sidebar, click Project Settings.
The Project Settings page displays.
View and Configure Maintenance Window
To view and configure the maintenance window using the Atlas UI:
Click the Set Maintenance Window button to display the maintenance window settings.
Set the day and time that you want Atlas to start maintenance on your project.
If you want Atlas to automatically defer any scheduled maintenance for one week, click Automatically defer maintenance for one week.
To set a range of protected hours in which Atlas avoids performing standard updates, toggle the Turn on protected hours setting to On. You can set a maximum time range of 18 hours a day.
Click Save to keep your changes or click Cancel to discard them.
To return the details for the maintenance window using the Atlas CLI, run the following command:
atlas maintenanceWindows describe [options]
To update the maintenance window using the Atlas CLI, run the following command:
atlas maintenanceWindows update [options]
To learn more about the syntax and parameters for the previous commands, see the Atlas CLI documentation for atlas maintenanceWindows describe and atlas maintenanceWindows update.
Clear Your Maintenance Window Configuration Settings
If you configured a preferred maintenance window start time, you can clear the settings using the Atlas CLI or the Atlas UI. Clearing your maintenance window configuration restores the default maintenance window settings.
To clear the configured maintenance window using the Atlas UI, toggle the Set Maintenance Window setting to Off.
To clear the configured maintenance window using the Atlas CLI, run the following command:
atlas maintenanceWindows clear [options]
To learn more about the command syntax and parameters, see the Atlas CLI documentation for atlas maintenanceWindows clear.
Respond to Required Maintenance
When maintenance is required:
Atlas displays a banner in your project's cluster list showing the date and time when the maintenance is scheduled.
Between 48 and 72 hours before the scheduled maintenance, Atlas sends an email to users with the
Project Ownerrole and updates the Atlas UI to display the option to begin maintenance immediately or to defer maintenance for one week.Note
To configure how you receive scheduled maintenance window notifications, see Configure a Maintenance Window Alert.
Begin Maintenance Now
To begin maintenance immediately:
Click the banner. A modal window titled Scheduled Maintenance Operations appears. This window describes the content of the currently scheduled maintenace operation.
Click the Begin Now button. In the Start Cluster Maintenance Now modal, confirm by clicking Yes, start my maintenance now.
To update the maintenance window using the Atlas CLI, run the following command:
atlas maintenanceWindows update [options]
To learn more about the command syntax and parameters, see the Atlas CLI documentation for atlas maintenanceWindows update.
IMPORTANT: To trigger maintenance immediately, pass the
--startASAP option.
# Trigger immediate maintenance for the project with the ID # 5e2211c17a3e5a48f5497de3: atlas maintenanceWindows update --startASAP --projectId 5e2211c17a3e5a48f5497de3 --output json
Atlas provides the Update One
Maintenance Window for One Project endpoint. You can trigger maintenance
immediately by passing in the optional startASAP field with
a value of true.
curl --user "${PUBLIC_KEY}:${PRIVATE_KEY}" \ --digest --include \ --header "Accept: application/vnd.atlas.2025-03-12+json" \ --header "Content-Type: application/json" \ -X PATCH "https://cloud.mongodb.com/api/atlas/v2/groups/{groupId}/maintenanceWindow" \ --data ' { "startASAP": true }'
Defer Maintenance
To defer scheduled maintenance:
Click the banner. A modal window titled Scheduled Maintenance Operations appears. This window describes the content of the currently scheduled maintenace operation.
Click the Defer 1 Week button. In the Defer Maintenance to Next Week modal, confirm by clicking Yes, defer maintenance until next week.
To defer the maintenance window using the Atlas CLI, run the following command:
atlas maintenanceWindows defer [options]
To learn more about the command syntax and parameters, see the Atlas CLI documentation for atlas maintenanceWindows defer.
Atlas provides the Defer One Maintenance Window for One Project endpoint.
Note
You can defer a single project maintenance event up to two times.
Maintenance Version Upgrades during Maintenance Windows
If Atlas will upgrade the MongoDB maintenance version on one of your clusters during the next maintenance window, the cluster's card displays the target MongoDB maintenance version.