[SERVER-41289] fix WiredTigerKVEngine::setStableTimestamp(force=true) Created: 23/May/19  Updated: 29/Oct/23  Resolved: 29/May/19

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

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2019-06-03
Participants:

 Description   

This function was originally intended to set the oldest, commit, and stable timestamps to the same value when "force" was set to true, but instead we only ended up setting the stable timestamp. See https://github.com/mongodb/mongo/commit/6f23d1a20a7669396efab06bf26b3ee76553fd9b



 Comments   
Comment by Githook User [ 29/May/19 ]

Author:

{'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}

Message: SERVER-41289 setStableTimestamp(force=true) always sets oldest and commit timestamps
Branch: master
https://github.com/mongodb/mongo/commit/1e369fabb0e4dece8e9ddeb486eb491def1e8d2e

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