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

secondaryDelaySecs upgrade FCV checks don't work when 4.9 becomes last-continuous

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0.0-rc0
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.9
    • Sprint:
      Repl 2021-04-19
    • Linked BF Score:
      135

      Description

      This was discovered as fallout from SERVER-54434, which caused a few secondaryDelaySecs upgrade/downgrade tests to fail.

      Checks like this use kLatest when allowing secondaryDelaySecs. However, once kLatest becomes 5.0, those checks will incorrectly exclude 4.9. We need to make sure the upgrade/downgrade and reconfig paths for the delay field name work as expected when 4.9 becomes last-continuous.

      This is specifically an issue for upgrading shardsvrs from 4.4 to 4.9 and for downgrading shardsvrs from 5.0 to 4.9 where 4.9 is last-continuous and 5.0 is latest.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              pavithra.vetriselvan Pavithra Vetriselvan
              Reporter:
              pavithra.vetriselvan Pavithra Vetriselvan
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: