replica_set_multiversion tests can depend on standalones illegally downgrading

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.4.0-rc2, 4.7.0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Repl 2020-04-20
    • 46
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      replica_set_multiversion will randomly choose between "latest" and "last-stable" when starting up a mongod instance. The passthrough logic is smart enough to downgrade the FCV and clean shutdown, but that's not sufficient for ensuring "last-stable" is always able to start up in more complicated restart sequences. Consider the following (using 4.4/4.2 as an example):

      1. Start MongoDB 4.4 + ReplSet
      2. SetFCV 4.2
      3. Shutdown (MongoDB 4.2 can restart on these data files)
      4. Start MongoDB 4.4 + Standalone
      5. Shutdown (MongoDB 4.2 can not restart on these data files)

            Assignee:
            Jason Chan
            Reporter:
            Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: