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

Change writeConcern upconversion to majority for internal connections on config servers to instead uassert that the request was sent with majority writeConcern

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • 4.1.4
    • Sharding
    • None
    • Sharding

    Description

      There is at least one known place where a node in the cluster calls a config server command without passing majority writeConcern (where mapReduce with sharded output calls _configsvrShardCollection, which could be fixed by calling CommandHelpers::appendMajorityWriteConcern here), as discovered in this Evergreen patch that removed the upconversion logic entirely.

      One drawback of replacing the upconversion with a uassert is that our tests may not catch all places where majority writeConcern is not passed, so this may introduce a "breaking change": in the wild, the uassert will be triggered rather than the upconversion applied.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: