[SERVER-31387] oplog application conflates upserting with being in steady state replication Created: 04/Oct/17  Updated: 30/Oct/23  Resolved: 30/Oct/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.0-rc2

Type: Bug Priority: Blocker - P1
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-31384 applyOps should propagate oplog appli... Closed
is depended on by SERVER-31507 Add option to applyOps to fail on upg... Closed
Related
is related to SERVER-31019 Changing fCV during initial sync lead... Closed
is related to SERVER-21700 Do not relax constraints during stead... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2017-10-23, Repl 2017-11-13
Participants:

 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.



 Comments   
Comment by Githook User [ 30/Oct/17 ]

Author:

{'email': 'judah@mongodb.com', 'name': 'Judah Schvimer', 'username': 'judahschvimer'}

Message: SERVER-31387 oplog application conflates upserting with being in steady state replication
Branch: master
https://github.com/mongodb/mongo/commit/b49b20887cf13720c0e863d24da95cc0239889f8

Generated at Thu Feb 08 04:26:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.