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

Commands which write should take a write concern

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.5
    • Affects Version/s: None
    • Component/s: Write Ops
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Sharding 10 (02/19/16), Sharding 11 (03/11/16), Sharding 12 (04/01/16), Sharding 13 (04/22/16)

      All commands that perform writes on behalf of users should support specification of a writeConcern, in the same manner as the write commands (insert, update, delete), and should support returning write concern failures in the same manner, as well.

      Support for write concern with the findAndModify command was added in SERVER-6558.

      For this ticket, add the logic for handling writeConcern to the Command::run() function. We will also add a shouldWaitForWriteConcern() function to ReplClientInfo and a call to setShouldWaitForWriteConcern() in setLastOpToSystemLastOpTime().

            Assignee:
            judah.schvimer@mongodb.com Judah Schvimer
            Reporter:
            dan@mongodb.com Daniel Pasette (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: