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

Provide a generic mechanism for commands to enforce that they must be run with w:majority write concern

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Sharding
    • Replication

      Some commands (such as the _configsvr commands and the setFeatureCompatibilityVersion command) must always use w:majority write concern. Right now different commands take different approaches to enforcing this. We should decide on a single strategy for this, ideally one that leverages the existing write concern handling code in dbcommands.cpp and returns write concern errors as 'writeConcernError' fields in the command response, in line with how the batch write commands report write concern errors

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: