[COMPASS-4504] MongoDB Compass cause Atlas Disk I/O % above 90% Created: 18/Nov/20 Updated: 08/Aug/22 |
|
| Status: | Open |
| Project: | Compass |
| Component/s: | Atlas, Performance |
| Affects Version/s: | 1.23.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yang Liu | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
macOS 10.15.7, M40 with 3 shards |
||
| Attachments: |
|
| Story Points: | 5 |
| Description |
| Comments |
| Comment by Yang Liu [ 02/Feb/21 ] | ||
|
Hi, thanks for looking into this and I'm really sorry for the late reply. I run each command for about 5 minutes, and didn't get alerts or seeing any I/O peak in the Atlas "Realtime" monitor. When I use Compass to show the same collection, I does show the alerts. (But I cannot catch a obvious peak in the "Realtime" monitor either) The collection size being tested is as below
| ||
| Comment by Massimiliano Marcon [ 18/Nov/20 ] | ||
|
yang@thatgamecompany.com can you connect with the shell and run:
and
(replacing collection with the name of your sharded collection. and check if in both cases you see the same spike in I/O you saw with Compass? | ||
| Comment by Yang Liu [ 18/Nov/20 ] | ||
|
As a note, we had a consultant session with Karan from MongoDB who witnessed the issue we had. |