[SERVER-48559] Exhaust cursor doesn't update lastKnownCommittedOpTime on 4.2 Created: 03/Jun/20  Updated: 29/Oct/23  Resolved: 04/Jun/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.4.0-rc9

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-06-15
Participants:
Linked BF Score: 11

 Description   

When syncing from 4.4, the exhaust cursors update lastKnownCommittedOpTime after sending out a batch so that it will wait for new data in the next round of getMore. However, we don't have that on 4.2 branch. So lastKnownCommittedOpTime stays stale and because of commit point propagation, a 4.2 sync source keeps sending out empty batches to 4.4 syncing nodes.



 Comments   
Comment by Githook User [ 04/Jun/20 ]

Author:

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

Message: SERVER-48559: Only use exhaust cursors for oplog fetching in FCV 4.4
Branch: v4.4
https://github.com/mongodb/mongo/commit/07052728f13cd1f4906f00c698f78145f40a6d18

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