-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Blocker - P1
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Repl 2017-10-23, Repl 2017-11-13
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We have one boolean that controls both of these behaviors. We upsert during steady state replication for rollback and startup recovery, though it may not be correct according to SERVER-21700. applyOps also decides if we should upsert based on it's "alwaysUpsert" flag. We also use this flag for determining if we should fail renames or upgrades/downgrades, which is completely orthogonal.
- is depended on by
-
SERVER-31384 applyOps should propagate oplog application mode
-
- Closed
-
-
SERVER-31507 Add option to applyOps to fail on upgrade/downgrade
-
- Closed
-
- is related to
-
SERVER-31019 Changing fCV during initial sync leads to divergent data across replica set members
-
- Closed
-
-
SERVER-21700 Do not relax constraints during steady state replication
-
- Closed
-