[SERVER-85705] Use lastWritten opTime for sync source selection Created: 25/Jan/24  Updated: 26/Jan/24

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Wenbin Zhu Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: PM-3489-Milestone-LastWrittenOpTime-CP
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-85599 [Milestone] LastWritten OpTime Checkp... In Progress
Assigned Teams:
Replication
Participants:

 Description   

Sync source selection uses the lastApplied opTime to check for the recency of nodes and decides if we can sync from a sync source candidate or if we should change our current sync source (see one of the example use cases here). We should instead use the lastWritten opTime for such recency checks.


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