-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2017-10-02, Repl 2017-10-23
Rollback will not work if there are a mix of UUID and non-UUID operations in the oplog.
- depends on
-
SERVER-31019 Changing fCV during initial sync leads to divergent data across replica set members
-
- Closed
-
-
SERVER-31531 feature compatibility version writes must check for writeErrors
-
- Closed
-
- is related to
-
SERVER-31384 applyOps should propagate oplog application mode
-
- Closed
-
- related to
-
SERVER-31426 Fail write to fCV document if admin.system.version collection does not have UUID
-
- Closed
-
-
SERVER-31805 rollbackViaRefetchNoUUID fails if rollback occurs during upgrade
-
- Closed
-