Upgrade from v8.0-v8.2 to v8.3 may crash if a cluster parameter contains an unknown field

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      The ticket SERVER-117009, which landed in v8.3, enabled the parsing strictness on a couple of cluster parameters, like fleCompactionOptions or internalSearchOptions.
      This causes an issue when upgrading: if any unknown field was persisted in a previous version, the node will crash immediately after upgrading the binaries to v8.3.

      Therefore, the commit done under SERVER-117009 must be reverted before the release v8.3 rolls out.

            Assignee:
            Silvia Surroca
            Reporter:
            Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: