-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Replication
-
None
-
None
-
None
-
None
-
None
-
None
-
None
One pain point associated with FCV right now is that there is no guarantee that an FCV transition happens in the same order with respect to other oplog entries on the primary and secondaries, which means that for a given oplog entry, if we were to check the FCV while applying the oplog entry on both the primary and the secondary, they may not have the same FCV. We should investigate if we can serialize this so that it happens in the same order on all nodes.
- is related to
-
SERVER-79269 Invariant that we don't check FCV in oplog application
-
- Open
-
-
SERVER-99559 Investigate the implications of replicating the OFCV through the oplog
-
- Closed
-