[DOCS-3924] Comment on: "manual/core/write-concern.txt" Created: 19/Aug/14 Updated: 16/Mar/15 Resolved: 23/Sep/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.11 |
| Type: | Improvement | Priority: | Blocker - P1 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: http://docs.mongodb.org/manual/core/write-concern/ |
||
| Participants: | |
| Days since reply: | 9 years, 21 weeks, 1 day ago |
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 23/Sep/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |