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

Commands that do writes on mongos should take a writeConcern and aggregate results

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

      Currently only write commands and user management commands handle writeConcern on mongos. They forward the command to each shard and then aggregate the responses and errors back together. Every command that does writes should do this. Commands just need to make sure that writeConcern is sent with the command to each shard and if multiple writeConcernErrors are returned, they need to be combined. If multiple error codes are returned, the error code should be 64 (writeConcernError).

            Assignee:
            judah.schvimer@mongodb.com Judah Schvimer
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: