-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
Execution Team 2019-07-15, Execution Team 2019-07-29, Execution Team 2019-08-12, Execution Team 2019-08-26, Execution Team 2019-09-09, Execution Team 2019-09-23
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
For some reason, it is reading from a data collection and then from the oplog collection in one transaction, which is preventing our code from enforcing that oplog collection reads must be the first in a transaction (so that oplog visibility rules can be enacted at the beginning of the txn).
- causes
-
SERVER-43412 Create a wrapper around getCursor calls for the oplog collection that ensures oplog visibility rules are enforced
-
- Closed
-