[SERVER-71145] Allow observed all_durable to move backward Created: 07/Nov/22  Updated: 29/Oct/23  Resolved: 08/Nov/22

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

Type: Improvement Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-45147 "Ghost" timestamp must set transactio... Closed
related to SERVER-71148 AllDurableTimestamp test does not enf... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-11-14
Participants:
Linked BF Score: 5

 Description   

The all_durable timestamp is maintained by the storage engine and may move backward. In the MongoDB integration with WT, we keep track of the highest seen all_durable and use that instead if the all_durable returned from WT is lower. This behavior was previously necessary due to ghost timestamps. Now with ghost timestamps having given up the ghost, we should be able to remove this and simply always return the all_durable that WT reports.



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

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-71145 Allow observed `all_durable` to move backward
Branch: master
https://github.com/mongodb/mongo/commit/36133c3b97aed247975af7940fb3b14ac40b38cc

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