[SERVER-85702] Use lastWritten opTime for secondary's term check when learning the commit point Created: 25/Jan/24  Updated: 07/Feb/24

Status: In Code Review
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Wenbin Zhu Assignee: Kishore Devireddy
Resolution: Unresolved Votes: 0
Labels: PM-3489-Milestone-LastWrittenOpTime-CP, PM-3489-perf-testing-required
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
Sprint: Repl 2024-02-05, Repl 2024-02-19
Participants:

 Description   

Secondaries perform a term check when learning the commit point to ensure the commit point is on the same branch of oplog history. Currently this term check compares the term of the new commit point against the term of this secondary’s lastApplied opTime. We will need to use the term of the lastWritten opTime instead.

Assignee should read the related code (including the call sites of this function) to make sure this is correct.


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