[SERVER-20224] Commands which write should take a write concern Created: 31/Aug/15  Updated: 05/Jul/16  Resolved: 12/Apr/16

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

Type: Bug Priority: Major - P3
Reporter: Daniel Pasette (Inactive) Assignee: Judah Schvimer
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-7637 Commands that take a writeConcern Closed
Duplicate
is duplicated by SERVER-3785 Add WriteConcern option to Map/Reduce Closed
Related
related to SERVER-22414 Remove old writeConcern handling code... Closed
related to DRIVERS-290 Support sending writeConcern for comm... Closed
related to SERVER-22540 Commands that do writes on mongos sho... Closed
related to SERVER-22769 cleanupOrphaned has duplicated writeC... Closed
related to SERVER-23995 Expand writeConcern-aware command lis... Closed
related to SERVER-6558 findAndModify should take a write con... Closed
is related to SERVER-24191 Bump wire version to indicate improve... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 10 (02/19/16), Sharding 11 (03/11/16), Sharding 12 (04/01/16), Sharding 13 (04/22/16)
Participants:

 Description   

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



 Comments   
Comment by Githook User [ 09/May/16 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-20224 Now only the command processor calls txn->setWriteConcern()

It also restores the original writeConcern when it is done.
Branch: master
https://github.com/mongodb/mongo/commit/3555c1363e02c64511d8826a57289275c13491c0

Comment by Githook User [ 21/Apr/16 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-20224 correctly check for BatchedCommandResponse parse errors in user management commands
Branch: master
https://github.com/mongodb/mongo/commit/02c99b06d19a7cbcbf2ab867907f7b2ebac8c818

Comment by Githook User [ 12/Apr/16 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-20224 commands that do writes take a writeConcern
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/017d96e1665b11c8cfacee376e2bbaa288fdf079

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-20224 commands that write support writeConcern
Branch: master
https://github.com/mongodb/mongo/commit/7ed530a55304bd9cc2b80c054f379b10d9cea8e2

Generated at Thu Feb 08 03:53:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.