[DOCS-9475] Docs for SERVER-26748: Don't call for priority takeover when repl lagged Created: 02/Dec/16 Updated: 30/Oct/23 Resolved: 17/Mar/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Emily Hall | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | code-and-test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 46 weeks, 6 days ago | ||||||||
| Description |
|
Engineering Ticket Description: Currently in pv1 we call for priority takeover without concern for whether the higher priority node is caught up in replication, which can lead to unnecessary rollbacks of w:1 writes. If we avoid calling for an election due to priority takeover if we are more than X seconds repl lagged, then that in combination with the catchup period should prevent any writes from being lost during priority takeover. |
| Comments |
| Comment by Sarah Olson [ 17/Mar/23 ] |
|
Closing this out on the grounds that:
Based on this, closing as WON'T DO. Please don't hesitate to give me a shout or to reopen if you disagree. |