[SERVER-75081] OplogTruncateMarkers don't preserve OplogStone legacy initialisation behavior Created: 21/Mar/23  Updated: 29/Oct/23  Resolved: 28/Mar/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Haley Connelly Assignee: Haley Connelly
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: Execution Team 2023-04-03
Participants:
Linked BF Score: 20

 Description   

There is a difference between OplogTruncateMarkers and legacy OplogStones on how to determine whether to sample or scan the existing oplog recordstore.

Prior to SERVER-46870, the OplogStones (now renamed OplogTruncateMarkers) were computed via scanning based on "numStonesToKeep".

 

Post SERVER-46870, scanning is performed pending a constraint that isn't equivalent unless dataSize were equivalent to the maxSize. 



 Comments   
Comment by Githook User [ 24/Mar/23 ]

Author:

{'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}

Message: SERVER-75081 Preserve OplogStone initialization behavior in OplogTruncateMarkers
Branch: master
https://github.com/mongodb/mongo/commit/5ad203a0e39df64c86e94c56de848d9add02adbc

Generated at Thu Feb 08 06:29:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.