[DOCS-9531] Docs for SERVER-24497: implement noop writes to test for primary-ship Created: 05/Dec/16 Updated: 27/Jul/17 Resolved: 27/Jul/17 |
|
| 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: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 6 years, 28 weeks, 6 days ago | ||||||||
| Epic Link: | PM-173 | ||||||||
| Description |
|
Engineering Ticket Description: If the read is successful (returns no error otherwise and all locks are released), we then: Generate noop writes that should be replicated to a majority of secondary nodes. When awaitReplication returns, then the primary will know it is the true primary of the set. |
| Comments |
| Comment by Kay Kim (Inactive) [ 27/Jul/17 ] |
|
seems like an accidental docs changes needed. |