[SERVER-63442] Refactor WTRecordStoreCursor timestamp fields Created: 08/Feb/22  Updated: 05/Jun/23

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

Type: Improvement Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: techdebt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Participants:

 Description   

Oplog cursors keep around two timestamps as state. The traditional visibility "no holes" time and SERVER-63308 introduced _readTimestampForOplog.

Given visibility should ultimately be the minimum of the two values (when they both exist), it doesn't seem necessary to have two variables. However, an initial effort to make that reduction failed.

I speculate some of the complexity has to do with oplog visibility being reset on _txnClose, but the _timestampReadSource is not. It's unclear what callers rely on those semantics.


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