[SERVER-41448] TransactionHistoryIterator should always do untimestamped reads Created: 31/May/19  Updated: 29/Oct/23  Resolved: 10/Jun/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.2.0-rc1, 4.3.1

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:
Backports
Depends
Duplicate
is duplicated by SERVER-41558 Make CollectionScan on oplog work wit... Closed
Related
related to SERVER-41558 Make CollectionScan on oplog work wit... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Repl 2019-06-17
Participants:
Linked BF Score: 12

 Description   

SERVER-41178 fixed the timestamp read issue in rollback recovery, but doing timestamp read with unset last applied may also make oplog writes invisible in initial sync.



 Comments   
Comment by Githook User [ 11/Jun/19 ]

Author:

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

Message: SERVER-41448: TransactionHistoryIterator should only take global IS lock and use caller's read source

(cherry picked from commit e297640646d2b38401698ab5e77c3770614b6d69)
Branch: v4.2
https://github.com/mongodb/mongo/commit/41bf8a1db10f682aad8b7b28a98c4f2f062931d4

Comment by Githook User [ 10/Jun/19 ]

Author:

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

Message: SERVER-41448: TransactionHistoryIterator should only take global IS lock and use caller's read source
Branch: master
https://github.com/mongodb/mongo/commit/e297640646d2b38401698ab5e77c3770614b6d69

Generated at Thu Feb 08 04:57:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.