[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: |
|
||||||||||||
| 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 |
| 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 |