[SERVER-37975] Remove _oplogMaxAtStartup in WiredTigerOplogManager Created: 06/Nov/18  Updated: 29/Oct/23  Resolved: 09/Nov/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.6

Type: Task Priority: Major - P3
Reporter: Xiangyu Yao (Inactive) Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-11-19
Participants:

 Description   

We no longer need _oplogMaxAtStartup as the lower bound for visibility timestamp because we explicitly set oplogReadTimestamp to be the same value as _oplogMaxAtStartup on startup and it will only grow beyond that value.

Code and comments related to this variable can be removed.



 Comments   
Comment by Githook User [ 08/Nov/18 ]

Author:

{'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com', 'username': 'xy24'}

Message: SERVER-37975 Remove '_oplogMaxAtStartup' in WiredTigerOplogManager
Branch: master
https://github.com/mongodb/mongo/commit/b0d400815c3159b4cb30b6818138fc55036f8ed4

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