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

Clean shutdown of secondaries should occur in between oplog batches, not during

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.2.5
    • 3.2.9
    • Replication
    • Fully Compatible
    • ALL
    • Repl 17 (07/15/16)

    Description

      Starting in MongoDB version 3.2, replica set secondaries write entries to the oplog concurrently with applying the changes described by those oplog entries to the data files. Because of this change, starting in MongoDB 3.2, the singleton document in local.replset.minvalid contains a "begin" field during periods of oplog application, indicating the newest oplog entry not in the current batch of oplog entries being applied.

      In order to properly downgrade from 3.2 to 3.0, which ignores the "begin" field, 3.2 secondary nodes should only shut down cleanly at oplog batch boundaries, not in the middle of applying a batch.

      Attachments

        Issue Links

          Activity

            People

              mathias@mongodb.com Mathias Stearn
              schwerin@mongodb.com Andy Schwerin
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: