[SERVER-31387] oplog application conflates upserting with being in steady state replication - MongoDB Jira

XML

Word

Printable

JSON

Details

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

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Repl 2017-10-23, Repl 2017-11-13

Description

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.

Attachments

Issue Links

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

Activity

People

Assignee:: Judah Schvimer

Reporter:: Judah Schvimer

Participants:: Githook User, Judah Schvimer

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: Oct 04 2017 06:54:43 PM UTC

Updated:: Dec 06 2017 09:11:22 PM UTC

Resolved:: Oct 30 2017 08:50:28 PM UTC