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

Arbiters do not track FCV changes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.8
    • Labels:
      None
    • Backwards Compatibility:
      Minor Change
    • Operating System:
      ALL
    • Sprint:
      Repl 2018-07-02, Repl 2018-07-16, Storage NYC 2019-02-11

      Description

      Because arbiters do not track FCV (since they do not follow the oplog and thus do not currently know when it is upgraded), the WiredTiger data format for arbiters is stuck on 2.9 (the version associated with MongoDB 3.2). We must keep dragging along the parsing code and associated test code for that version for each new release of MongoDB, indefinitely.

      Some ways to fix this would be:

      • upgrade arbiters to the 4.2 data format immediately, the first time a 4.2 binary is run, and change the downgrade instructions to delete all arbiter datafiles on downgrade.
      • change the way FCV changes are propagated so arbiters hear about them.
      • deprecate and remove support for non-replicating arbiters.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              daniel.gottlieb Daniel Gottlieb
              Reporter:
              milkie Eric Milkie
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: