- Alerts and Monitoring >
- Alerts >
- Alert Resolutions >
- Disk I/O % Utilization
Disk I/O % Utilization¶
Description¶
Disk I/O % Utilization alerts indicate that percentage of time
during which issued requests reaches a specified threshold. You set
this threshold when you create the alert.
Note
The utilization measurements for the following alerts include requests from all processes, not just MongoDB processes.
Disk I/O % utilization on Data Partition occurs if the percentage of time during which requests are being issued to any partition that contains the MongoDB collection data meets or exceeds the threshold.
Disk I/O % utilization on Index Partition occurs if the percentage of time during which requests are being issued to any partition that contains the MongoDB index data meets or exceeds the threshold.
Disk I/O % utilization on Journal Partition occurs if the percentage of time during which requests are being issued to the partition that contains the MongoDB journal meets or exceeds the threshold.
Possible Observations¶
To observe high percentage of Disk I/O utilization, open the Hardware Metrics section of the Metrics tab and find the following metrics:
| Graph | Indicator |
|---|---|
| Util% | High value |
| Disk IOPS | IOPS value greater than the provisioned IOPS value |
| Normalized System CPU | High IOWait curve IOWait measures the percentage of time the CPU runs idle waiting for an I/O operation to complete. |
Common Triggers¶
A few common events may lead to high Disk I/O % Utilization and trigger these alerts:
- Unoptimized queries
- A one-time event that spikes disk utilization, such as an index build.
Possible Solutions¶
Consider the following resolutions to resolve Disk I/O %
Utilization alerts:
Use the MongoDB Atlas Performance Advisor to view slow queries and suggested indexes.
Review Indexing Strategies for possible further indexing improvements.
Note
A temporary spike in disk utilization may result when creating new indexes.
Analyze Query Performance to review how your queries are using your indexes.
Use a faster disk drive with more hardware resources.
Move operations from disks with large workloads to different disks.