consistency/isolation/recency tracking ticket
(DOCS-5326)
|
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | mongodb-3.1.x |
| Type: | Sub-task | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Kyle Suarez |
| Resolution: | Done | Votes: | 0 |
| Labels: | 3.2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 29 weeks ago | ||||||||
| Description |
|
Per discussion in the comments of Highlights of the technique:
Caveats: Not all drivers support findAndModify with write concern. |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |
| Comment by Githook User [ 14/Jan/16 ] |
|
Author: {u'username': u'ksuarz', u'name': u'Kyle Suarez', u'email': u'kyle.suarez@mongodb.com'}Message: This explicitly details the reasons why one would require a "quorum read" over This commit also fixes some grammar and explicitly mentions that this technique Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 14/Jan/16 ] |
|
Author: {u'username': u'ksuarz', u'name': u'Kyle Suarez', u'email': u'kyle.suarez@mongodb.com'}Message: Rather than issuing a getLastError, you can use a write concern of ``majority`` Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 14/Jan/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: This cherry-picks 046152322b4fae3a98835ed74b718ef7d88f6da2 to apply it again, The changes in source/reference/write-concern.txt have been ignored in favor of Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by David Golden [ 08/Jan/16 ] |
|
I think you might want to address how this is different than readConcern level:majority.
More specifically, the opening paragraph is a bit confusing. I also think it's important to caveat that this technique has a substantial cost over read concern level::majority and should only be used when staleness is absolutely unacceptable. You have:
I would phrase it more like this:
Then the next paragraph opens "This tutorial outlines a procedure..." which directly addresses how I left the opening paragraph. Then before the "Prerequisites" paragraph is probably the right place to put the caveat about the latency cost of turning a read into a write. |
| Comment by Eric Milkie [ 04/Jan/16 ] |
|
Rescoped to version 3.2 of the manual only. In version 3.2 it should be possible to use the findAndModify technique as documented. |
| Comment by Githook User [ 11/May/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: Revert " This reverts commit 98a314ff56bdec972970f633cdcbc118182bc98c. |
| Comment by Githook User [ 11/May/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: Revert " This reverts commit 046152322b4fae3a98835ed74b718ef7d88f6da2. |
| Comment by Githook User [ 11/May/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: Revert " This reverts commit fc5e1bd7d9081791940a00e538b224db8903653f. |
| Comment by Githook User [ 11/May/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: Revert " This reverts commit fc5e1bd7d9081791940a00e538b224db8903653f. |
| Comment by Shannon Bradshaw (Inactive) [ 11/May/15 ] |
|
Raised in the driver leads meeting this morning, "I don't think you can really do this with any driver yet, since both ops have to be on the same socket.". kay.kim@10gen.com let's unpublish this. We need to determine whether any drivers actually support this. If they don't, our proposed solution is misleading. |
| Comment by Githook User [ 08/May/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 08/May/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 08/May/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 08/May/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |