[SERVER-79322] Modify collection lock assertion when creating random cursor executor Created: 25/Jul/23 Updated: 29/Oct/23 Resolved: 25/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution NAMR Team 2023-08-07 | ||||||||
| Participants: | |||||||||
| Description |
|
When creating a random cursor executor we assert that the collection is locked, but this may not be the case if we are in a lock-free read. |
| Comments |
| Comment by Githook User [ 25/Jul/23 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |