Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-31387

oplog application conflates upserting with being in steady state replication

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Blocker - P1 Blocker - P1
    • 3.6.0-rc2
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2017-10-23, Repl 2017-11-13
    • None
    • None
    • None
    • None
    • None
    • None
    • 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.

            Assignee:
            judah.schvimer@mongodb.com Judah Schvimer
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: