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

Replica set reconfiguration should check it's not removing a custom write concern which is set as the default

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Repl 2022-02-21, Repl 2022-03-07, Repl 2022-03-21, Repl 2022-04-04, Repl 2022-04-18

      As specified here: https://docs.mongodb.com/manual/reference/replica-configuration/#mongodb-rsconf-rsconf.settings.getLastErrorModes Custom-named write concerns can be set in the config, and then used as the default write concern. Currently, we can have the case where the default write concern is a custom write concern, and then the replica set is reconfigured to remove the custom write concern, so we are left with an invalid default write concern. Checks should be added to ensure such a reconfig fails.

            Assignee:
            vesselina.ratcheva@mongodb.com Vesselina Ratcheva (Inactive)
            Reporter:
            gabriel.marks@mongodb.com Gabriel Marks
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: