Problem Statement/Rationale

What is going wrong? What action would you like the Engineering team to take?

For large collection (13M documents in my case) the bulk delete operation shows an error in the GUI, however it correctly deletes the documents in the collection "in the background" (but it takes 20-30 minutes).

Please be sure to attach relevant logs with any sensitive data redacted.
How to retrieve logs for: Compass; Shell

Compass log:

Unknown macro: {"t"}

,"s":"D1","c":"COMPASS-DATA-SERVICE","id":1001000022,"ctx":"Connection 0","msg":"Server heartbeat succeeded","attr":{"connectionId”:”*******:27017","duration":64}}

Unknown macro: {"t"}

,"s":"D1","c":"COMPASS-DATA-SERVICE","id":1001000030,"ctx":"Connection 0","msg":"Driver command failed","attr":{"address":"*******:27017","serverConnectionId":11,"duration":300010,"commandName":"delete","failure":"connection 11 to *******:27017 timed out"}}

Unknown macro: {"t"}

,"s":"E","c":"COMPASS-DATA-SERVICE","id":1001000058,"ctx":"Connection 0","msg":"Failed to perform data service operation","attr":{"op":"deleteMany","message":{},"ns":"*******"}}

Unknown macro: {"t"}

,"s":"E","c":"COMPASS-CRUD-UI","id":1001000268,"ctx":"Bulk Delete Documents","msg":"Delete operation failed: connection 11 to *******:27017 timed out","attr":{"stack":"MongoNetworkTimeoutError: connection 11 to *******:27017 timed out\n    at Timeout._onTimeout (file:///Applications/MongoDB%20Compass.app/Contents/Resources/app.asar/build/457.62ff507227e440b5b770.renderer.js:134:641388)\n    at listOnTimeout (node:internal/timers:581:17)\n    at process.processTimers (node:internal/timers:519:7)","name":"MongoNetworkTimeoutError","message":"connection 11 to *******:27017 timed out","code":null}}

 

Steps to Reproduce

How could an engineer replicate the issue you’re reporting?

Create an M30 cluster on MongoDB Atlas (2 secondary, 1 primary replica set) with a few collections that have over 13M documents. Try bulk deleting documents in one of the collections from the Compass GUI.

Expected Results

I receive an information/warning that the collection size is above XYZ (your tested size that doesn't timeout) and the delete operation will happen in the background.

Actual Results

What do you observe is happening?

I receive the error "The delete operation failed." which is not true, because the delete operation continues in the background and eventually finishes.

Additional Notes

Any additional information that may be useful to include.

Tested on collections with 13M and 82M documents on the MongoDB Atlas M30-M40 cluster.