Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-14440

Investigate changes in SERVER-56241: Don't allow setting getLastErrorDefaults on startup/reconfig

    XMLWordPrintableJSON

Details

    Description

      Description

      Downstream Change Summary

      We do not allow setting settings.getLastErrorDefaults in the config to a customized value, i.e anything other than:

          {w: 1, wtimeout: 0}
          

      on startup/reconfig

      Description of Linked Ticket

      • 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.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

      Attachments

        Activity

          People

            ian.fogelman@mongodb.com Ian Fogelman
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              2 years, 23 weeks, 5 days ago