[DOCS-9519] Docs for SERVER-23663: New primary syncs from chosen node to catch up with timeout Created: 05/Dec/16  Updated: 30/Oct/23  Resolved: 07/Oct/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

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:
Documented
documents SERVER-23663 New primary syncs from chosen node to... Closed
Duplicate
duplicates DOCS-8259 catchUpTimeoutMillis replica set conf... Closed
Participants:
Days since reply: 7 years, 10 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Engineering Ticket Description:

To avoid unnecessary rollback after a PV1 election, the new primary finds the node with the highest lastOpTime, then tries to sync all the oplog from that node to catch up its opTime. This ticket is for the catch-up phase.

If the catch-up timeout expires before we exhaust all the sync source’s oplog entries, the new primary ends the catch-up phase and proceeds to exit drain mode like normal.
If the query from the remote node fails, treat the same as if the catch-up timeout expired. Do not attempt to choose a new sync source.


Generated at Thu Feb 08 07:58:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.