[DOCS-13633] Docs should recommend using causal consistency to get read-your-writes Created: 05/May/20 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | docs-query | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
DescriptionI was looking at the documentation of geoSearch, and I noticed that we state: To ensure that a single thread can read its own writes, use "majority" read concern and This is no longer our current recommendation. As of 3.6, we recommend using causal consistency (with majority read concern and majority write concern) in order to get read-your-writes behavior. When causal consistency is enabled for the session, it's no longer necessary to perform all operations against the primary. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |