[SERVER-77030] Server can return invalid BSON while collection is being dropped Created: 11/May/23  Updated: 11/May/23  Resolved: 11/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Michael McClimon Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Operating System: ALL
Steps To Reproduce:

We've seen this intermittently, but have not been able to reliably reproduce it; it feels like a race condition in the server to me.

Participants:

 Description   

I was looking at a mongosync BF (REP-2554), and it looks like we get invalid BSON from an insert command immediately after / while a collection is dropped. The error we actually see is an InsufficientBytesError from the Go driver, which happens when it tries to read an i32 out of the BSON and there aren’t enough bytes left to do so.

The drop command for test.wildcard_cache_plans starts in the logs here: https://parsley.mongodb.com/resmoke/e8821e83ed64ef6dcb9ff38da048fa66/all?bookmarks=0,531483,531522,590010,597170&shareLine=531483. The mongosync crash is at line 531522, "too few bytes to read next component".



 Comments   
Comment by Michael McClimon [ 11/May/23 ]

max.hirschhorn@mongodb.com suggests on Slack that this is unlikely to be a bug in the server, and that at the very least this ticket is unactionable without some more logging on our end, so I'll close this for now.

Generated at Thu Feb 08 06:34:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.