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().
- is duplicated by
-
SERVER-3785 Add WriteConcern option to Map/Reduce
- Closed
- is related to
-
SERVER-24191 Bump wire version to indicate improved support for write concern with commands
- Closed
- related to
-
SERVER-22414 Remove old writeConcern handling code from all commands
- Closed
-
DRIVERS-290 Support sending writeConcern for commands that write
- Closed
-
SERVER-22540 Commands that do writes on mongos should take a writeConcern and aggregate results
- Closed
-
SERVER-22769 cleanupOrphaned has duplicated writeConcern
- Closed
-
SERVER-23995 Expand writeConcern-aware command list in readConcern passthrough
- Closed
-
SERVER-6558 findAndModify should take a write concern
- Closed