[DOCS-8300] Commands that write should take a write concern Created: 12/Jul/16  Updated: 06/Dec/22  Resolved: 16/Sep/16

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 3.4 Core Server

Type: Task Priority: Major - P3
Reporter: Ramon Fernandez Marina Assignee: Andrew Aldridge
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
Duplicate
duplicates DOCS-7637 Commands that take a writeConcern Closed
Participants:
Days since reply: 7 years, 22 weeks, 2 days ago

 Description   
Project Summary, Updated 2016-04-13

Summary

Commands that write replicated database data should support accepting a write concern.

Motivation

In the earlier versions of MongoDB, the getLastError command is the only way for the user to wait until a write has been replicated to at least the specified amount of nodes. However, the semantics of this command is that it will wait for the last write on the current connection. This means that each connection needs to keep a state for remembering the last write. If commands that do writes accept a write concern, then the extra bookkeeping will be unnecessary and it will also reduce the amount of round trip to perform the same task by one. As of v3.2, there are a subset of commands that already accepts writeConcern as one of it’s parameters. These are the write commands, auth related commands that do database writes and findAndModify.

Documentation

Scope Document
Design Document



 Comments   
Comment by Emily Hall [ 12/Sep/16 ]

Commands from the scope document:

aggregate with $out
applyOps
clone
cloneCollection
cloneCollectionAsCapped
collMod
convertToCapped
copydb
create
createIndexes
drop
dropDatabase
dropIndexes
emptyCapped
mapReduce with $out
renameCollection

Generated at Thu Feb 08 07:56:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.