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

Starting replica set member standalone can lose committed writes starting in MongoDB 4.0

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Works as Designed
    • Affects Version/s: 4.0.0
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      ALL
    • Sprint:
      Repl 2018-12-03

      Description

      Starting in 4.0 we do recovery at startup (for everything but the oplog) by replaying the oplog instead of by journaling. However this is not done by default if a replica set member is started standalone, so we can lose committed writes in this case. Restarting a replica set member standalone is a common documented maintenance procedure, so losing committed writes in this case seems possibly problematic. This is also a change in behavior from 3.6.

      There is an undocumented parameter to do oplog replay when started as standalone; suggest that this should be enabled by default.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              judah.schvimer Judah Schvimer
              Reporter:
              bruce.lucas Bruce Lucas
              Participants:
              Votes:
              1 Vote for this issue
              Watchers:
              16 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: