[SERVER-83930] Investigate Assertion failure: _unindex failed ObjectIsBusy Created: 06/Dec/23  Updated: 24/Jan/24  Resolved: 24/Jan/24

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

Type: Task Priority: Major - P3
Reporter: Louis Williams Assignee: Dan Larkin-York
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-66503 ObjectIsBusy thrown in unindex Closed
related to SERVER-70503 Do not swallow exceptions when uninde... Backlog
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2024-02-05
Participants:

 Description   

Investigate this non-fatal error message. We should determine if this presents a problem, and if not, consider removing this assertion.



 Comments   
Comment by Louis Williams [ 06/Dec/23 ]

This is not an error and the assertion has been eliminated by SERVER-66503

Comment by Gregory Noma [ 06/Dec/23 ]

louis.williams@mongodb.com That sounds right to me. The only reason we would want to pursue fixing this further is if we think it's too misleading/confusing and/or if we feel we might mask other errors by ignoring it

Comment by Louis Williams [ 06/Dec/23 ]

Thanks for finding that gregory.noma@mongodb.com! Since this is only happening on older branches, I suspect that we should just not pursue fixing this further and ignore these errors. Does that sound right?

Comment by Gregory Noma [ 06/Dec/23 ]

Looks like this is just SERVER-66503 since we didn't backport that fix. Note that this isn't actually an assertion, it just logs a message and prints a backtrace as described in SERVER-70503

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