[COMPASS-5988] MongoDB Compass causes the replicaset primary to crash Created: 28/Jul/22  Updated: 28/Jun/23  Resolved: 28/Jul/22

Status: Closed
Project: Compass
Component/s: Compass
Affects Version/s: 1.32.5
Fix Version/s: No version

Type: Bug Priority: Major - P3
Reporter: Nivi Mor Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Replicaset running on Ubuntu 18
MongoDB Compass running MacOS BigSur 11.6 with Intel


Attachments: Zip Archive mongodb_compass_log.zip    
Issue Links:
Duplicate
duplicates COMPASS-5316 Load dbStats and collInfo / collStats... Closed
Related
related to COMPASS-5387 Allow to disable all dbStats / collSt... Open
related to COMPASS-5316 Load dbStats and collInfo / collStats... Closed
Documentation Changes: Not Needed

 Description   

Problem Statement/Rationale

Connecting to replicaset using MongoDB Compass causes the primary to crash.

Please be sure to attach relevant logs with any sensitive data redacted.

Steps to Reproduce

Create a replicaset of 3 nodes, mongo version 5.0.9 community.

Connect to the replicaset using MongoDB compass version 1.32.5, using direct connect.

Expected Results

MongoDB Compass should connect successfully and display the collections. The replicaset primary should handle the connection and queries from MongoDB Compass without any significant load.

Actual Results

The amount of file descriptors (possible due to connections and queries) spikes in order of tens of thousands. This leads to too many files open and eventually a primary crash. Meanwhile this is happening, MongoDB Compass hangs and shows a blank screen.

Additional Notes

The database that causes MongoDB Compass to hang and the primary to crash weight about 4 terrabytes. We are using the direct connect option because we're opening an SSH tunnel from our local machines to the primary using a jumper server.



 Comments   
Comment by Nivi Mor [ 28/Jul/22 ]

Thanks for the prompt response Anna, I'll follow the jiras you mentioned.

Comment by Anna Henningsen [ 28/Jul/22 ]

nivi.mor@bigpanda.io Thank you, this is very helpful! Currently, Compass loads stats for all collections in a database once you navigate the collections list for that database. This is almost certainly what’s causing this issue.

We’re tracking related work in COMPASS-5316 and COMPASS-5387. I’d close this ticket as a duplicate, and you can follow our progress on this issues there.

Comment by Nivi Mor [ 28/Jul/22 ]

MongoDB Compass logs - mongodb_compass_log.zip

Comment by Anna Henningsen [ 28/Jul/22 ]

nivi.mor@bigpanda.io Can you provide Compass and/or server log files?

Generated at Wed Feb 07 22:41:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.