Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.6.0-rc1
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2017-10-02, Repl 2017-10-23
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Assignee:: Judah Schvimer
Reporter:: Judah Schvimer
Participants:: Eric Milkie, Githook User, Judah Schvimer
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Sep 20 2017 08:51:25 PM UTC
Updated:: Oct 30 2023 11:13:27 PM UTC
Resolved:: Oct 20 2017 02:46:56 PM UTC
Confidence Status Last Update:: 04/Oct/17 5:34 PM