[SERVER-46053] NewOplogFetcher should send term/lastCommittedOpTime in getMore request Created: 10/Feb/20  Updated: 29/Oct/23  Resolved: 11/Feb/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.3.4

Type: Bug Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-45468 Create a DBClientCursor in the new op... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-02-24
Participants:

 Description   

Similar to this unit test, we should call setCurrentTermAndLastCommittedOpTime before calling _cursor->more() in NewOplogFetcher to make the DBClientCursor send the term and lastKnownCommittedOpTime fields in the getMore request. This is needed for the first getMore request and when oplogFetcherUsesExhaust is off.



 Comments   
Comment by Githook User [ 11/Feb/20 ]

Author:

{'name': 'Lingzhi Deng', 'username': 'ldennis', 'email': 'lingzhi.deng@mongodb.com'}

Message: SERVER-46053: NewOplogFetcher should send term and lastCommittedOpTime in getMore requests
Branch: master
https://github.com/mongodb/mongo/commit/9f40a2e96b3ad0e5fc84956c153a938ed531e91f

Generated at Thu Feb 08 05:10:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.