-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Storage
-
Fully Compatible
-
ALL
-
v4.0
-
Storage NYC 2018-06-04, Storage NYC 2018-06-18
The evergreen patch shows that there could be a view cycle when we perform reads on the secondary node. Since collMod command won't succeed on the primary if it forms a cycle, this could be a bug for secondary reads.
Update:
Basically, view catalog could reload (loading view definitions from system.views to in-memory data structure) whenever a read comes and there is discrepancy between persistent version and in-memory version of view definition, even during oplog application. Thus, secondary reads could see inconsistent state of view catalog.
- is related to
-
SERVER-32883 Enhanced FSM testing for reading from secondaries
- Closed
- related to
-
SERVER-39950 Merge two oplog batching code paths
- Closed