-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
ALL
-
v3.6
-
Repl 2017-11-13, Repl 2017-12-04
When an applyOps oplog entry is applied, it always sets the "inSteadyStateReplication" flag to true for commands and to the "alwaysUpsert" value for operations.
This means that an applyOps command with a renameCollection command in it will not cause initial sync to restart.
We should pass the appropriate OplogApplication::Mode into the applyOps function.
- depends on
-
SERVER-31387 oplog application conflates upserting with being in steady state replication
- Closed
- related to
-
SERVER-31019 Changing fCV during initial sync leads to divergent data across replica set members
- Closed
-
SERVER-31507 Add option to applyOps to fail on upgrade/downgrade
- Closed
-
SERVER-31189 fassert if feature compatibility version changes during rollback
- Closed