Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
ALL
-
Execution Team 2023-04-03
-
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.