-
Type: Improvement
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
The fact that DBDirectClient is allowed to change the storage engine snapshot is the cause of many hard-to-reproduce bugs and many problems. DBDirectClient can early-returned in waitForReadConcern, which is already done for snapshot readConcern. Additionally, the logic in AutoGetCollectionForRead allows DBDirectClient to potentially change the storage engine snapshot while another AutoGetCollectionForRead has read from a different snapshot (see SERVER-41361).
We should investigate whether this behavior is actually necessary, and disallow it if possible.
- is related to
-
SERVER-41361 Do not read at lastApplied while already holding the PBWM lock on secondaries
- Closed