[SERVER-22540] Commands that do writes on mongos should take a writeConcern and aggregate results Created: 09/Feb/16  Updated: 26/Apr/16  Resolved: 12/Apr/16

Status: Closed
Project: Core Server
Component/s: Sharding, Write Ops
Affects Version/s: None
Fix Version/s: 3.3.5

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-23785 Remove ShardRegistry::kWriteConcernEr... Closed
is related to SERVER-20224 Commands which write should take a wr... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 10 (02/19/16), Sharding 11 (03/11/16), Sharding 12 (04/01/16), Sharding 13 (04/22/16)
Participants:

 Description   

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



 Comments   
Comment by Githook User [ 12/Apr/16 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-22540 Commands that do writes on mongos should take a writeConcern and aggregate results
Branch: master
https://github.com/mongodb/mongo/commit/889ca31c1a1e7725b14f291233a4ee4f7afea111

Generated at Thu Feb 08 04:00:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.