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

Don't allow setting getLastErrorDefaults on startup/reconfig

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0.0-rc0
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Minor Change
    • Sprint:
      Repl 2021-05-03, Repl 2021-05-17
    • Linked BF Score:
      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

              Assignee:
              huayu.ouyang Huayu Ouyang
              Reporter:
              huayu.ouyang Huayu Ouyang
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: