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

setDefaultRWConcern accepts invalid write concern options

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.3.0
    • None
    • None
    • Fully Compatible
    • ALL
    • Security 2022-01-24, Replication 2021-12-13, Replication 2021-12-27, Replication 2022-01-10
    • 167

    Description

      setDefaultRWConcern accepts invalid write concern options like {w: "1"}, but the server will error with UnknownReplWriteConcern when trying to do an actual write.

      We should either start accepting {w: "1"} or error at the time of setting the default read/write concern.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-61864 Replica set reconfiguration should check it's not removing a custom write concern which is set as the default

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

          Task - A task that needs to be done. SERVER-64309 Modify the server to support the setRWConcernDefault command directly against shardsvrs

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

          Activity

            People

              gabriel.marks@mongodb.com Gabriel Marks
              samy.lanka@mongodb.com Samyukta Lanka
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: