Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Blocker - P1
Fix Version/s: 3.6.0-rc2
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Repl 2017-10-23, Repl 2017-11-13
Confidence Status:
None
Work Order:
0

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
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

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

Created:: Oct 04 2017 06:54:43 PM UTC
Updated:: Oct 30 2023 11:13:07 PM UTC
Resolved:: Oct 30 2017 08:50:28 PM UTC
Confidence Status Last Update:: 19/Oct/17 4:06 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates