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

Take the oplog collection lock when updating the FCV document

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • Storage
    • None
    • ALL
    • Storage NYC 2018-03-12
    • 11

    Description

      This is necessary in order to prevent last-stable binary secondaries from seeing the FCV document change in the oplog collection BEFORE the primary bumps its internal wire version min and closes incoming connections with last-stable binaries. That would cause the last-stable binary secondary to crash.

      For example, if a v3.6 secondary obtains the 4.0 FCV value from the v4.0 binary primary's oplog, it will invariant and crash on seeing a BadValue: it only accepts 3.4 and 3.6 FCV field values.

      See the linked BF for further elaboration on HOW the secondary manages to acquire the oplog entry.

      Attachments

        Issue Links

          Activity

            People

              dianna.hohensee@mongodb.com Dianna Hohensee
              dianna.hohensee@mongodb.com Dianna Hohensee
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: