[SERVER-64200] Remove invariant stableTimestamp <= allDurableTimestamp already checked in WT Created: 04/Mar/22  Updated: 29/Oct/23  Resolved: 07/Mar/22

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

Type: Bug Priority: Major - P3
Reporter: Daniel Gomez Ferro Assignee: Daniel Gomez Ferro
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2022-03-07, Execution Team 2022-03-21
Participants:
Linked BF Score: 135

 Description   

Currently we are checking this invariant when setting the stable timestamp..

It is suspected that we can fetch a stale value for the all durable timestamp because we lack strong synchronization, which could make this invariant fail under some circumstances even though all durable is really greater than the stable timestamp.

Given that WT already checks the same property both for prepared transactions and for non-prepared transactions with the appropriate synchronization we can remove the check at this layer.



 Comments   
Comment by Githook User [ 04/Mar/22 ]

Author:

{'name': 'Daniel Gómez Ferro', 'email': 'daniel.gomezferro@mongodb.com', 'username': 'dgomezferro'}

Message: SERVER-64200 Remove invariant in WiredTigerKVEngine::setStableTimestamp
Branch: master
https://github.com/mongodb/mongo/commit/bac491bc8083025372cc3a948f0590311530759f

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