-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Execution Team 2020-09-21, Execution Team 2020-10-05
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.
- is depended on by
-
SERVER-50145 Have DDL operations and MODE_X writers install a new Collection object
- Closed
- related to
-
SERVER-50983 Add mode to AutoGetCollection to create collection if it doesn't exist
- Backlog