[SERVER-50984] Make query yielding aware of AutoGetCollection at high level Created: 16/Sep/20 Updated: 29/Oct/23 Resolved: 28/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.8.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Henrik Edin |
| 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 Team 2020-09-21, Execution Team 2020-10-05 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
With lock free reads, restoring locks and state after query yielding may cause Collection pointers held by AutoGetCollection and other helpers at a high level to be invalid and dangle. There might have come a MODE_X writer that installed a new Collection instance into the Collection catalog during the window where yield had the locks released. We need to add a way to pass any AutoGetCollection instances to the query plan executor so they can be notified to refresh their state when we restore after yield. |
| Comments |
| Comment by Githook User [ 26/Sep/20 ] |
|
Author: {'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}Message: It implements a yieldable interface that is used to re-load the CollectionPtr should be passed by const reference so a yield can notify |
| Comment by Githook User [ 26/Sep/20 ] |
|
Author: {'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}Message: |