[DOCS-9494] Docs for SERVER-24494: Parsing Linearizable Read command Created: 05/Dec/16 Updated: 23/Feb/18 Resolved: 23/Feb/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Emily Hall | Assignee: | Kay Kim (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 5 years, 50 weeks, 6 days ago | ||||||||
| Description |
|
Engineering Ticket Description: First step in implementing linearizable reads: implement read concern level. When a read is received with a read concern level “linearizable”, we must first check that the current node is master (available for writes). Nodes that are not currently in writable state shall return a NotMaster error. Linearizable reads are not permitted on Secondary nodes. If an afterOpTime read concern option is also supplied, a parse error is returned. To limit project scope, afterOpTime read concern option will be incompatible with read concern level linearizable, for now. Additionally, need to include unittests for parsing. |
| Comments |
| Comment by Kay Kim (Inactive) [ 23/Feb/18 ] |
|
Work done in another ticket before the ticket maker script |
| Comment by Ian Whalen (Inactive) [ 12/Feb/18 ] |
|
kay.kim just a heads up that I'm doing some cleanup and pulling tickets out from under resolved epics (including this one). |