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

Remove uassert for when newlyAdded field exists in setFeatureCompatibilityVersion

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • None
    • None
    • Repl 2021-08-23
    • 17

    Description

      FCV 4.4 doesn't know what the newlyAdded field is, and so we have code to make sure that the newlyAdded field doesn't exist in the config when trying to set the FCV. (Introduced in SERVER-46379.)

      Now, since we are on 5.1, we can only downgrade to 5.0, and that code can be removed.

      This ticket is similar: SERVER-48545.

      Attachments

        Issue Links

          duplicates

          Task - A task that needs to be done. SERVER-48545 Remove upgrade/downgrade support for initial sync semantics project on FCV 4.8

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Task - A task that needs to be done. SERVER-46379 Implement upgrade/downgrade support for Initial Sync Semantics

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-48545 Remove upgrade/downgrade support for initial sync semantics project on FCV 4.8

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              wenbin.zhu@mongodb.com Wenbin Zhu
              vishnu.kaushik@mongodb.com Vishnu Kaushik
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: