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

Don't allow setting getLastErrorDefaults on startup/reconfig

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.0.0-rc0
    • Replication
    • None
    • Minor Change
    • Repl 2021-05-03, Repl 2021-05-17
    • 159

    Description

      • We will fassert on startup if the field exists and is not {w:1, wtimeout: 0}

        for a replica set that is part of a sharded cluster, since that would be counter to our goal of ensuring that the default write concern is uniform across all replica sets in the cluster.

      • We will fail any addShard for a replica set that specifies something other than {w:1, wtimeout: 0}

        or any replSetReconfig commands that modify getLastErrorDefaults.

      • We should upgrade the existing startup warning for non {w:1, wtimeout: 0}

        values on non-shard servers from saying that this field is deprecated to say that the field is ignored.

      Attachments

        Issue Links

          Activity

            People

              huayu.ouyang@mongodb.com Huayu Ouyang
              huayu.ouyang@mongodb.com Huayu Ouyang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: