-
Type: Improvement
-
Resolution: Done
-
Priority: Blocker - P1
-
Affects Version/s: None
-
Component/s: manual
-
Labels:
-
Environment:
*Location*: http://docs.mongodb.org/manual/core/write-concern/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.143 Safari/537.36
*Referrer*: https://www.google.com/
*Screen Resolution*: 1440 x 900
*repo*: docs
*source*: core/write-concern
*Location*: http://docs.mongodb.org/manual/core/write-concern/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.143 Safari/537.36 *Referrer*: https://www.google.com/ *Screen Resolution*: 1440 x 900 *repo*: docs *source*: core/write-concern
This is confusing. The MongdoDB doc on acknowledged write concern leads with: "With a receipt acknowledged write concern, the mongod confirms the receipt of the write operation." This implies the acknowledgement is just of receipt of the write; it does NOT imply that the client waits for success to continue. However, in the caption to an illustrative diagram, the docs say: "The client waits for acknowledgment of success or exception." That is much clearer – and somewhat contradictory, i.e. the acknowledgement is of success/failure, not simply of "receipt" of the write.