[SERVER-71148] AllDurableTimestamp test does not enforce proper all_durable semantics Created: 07/Nov/22  Updated: 29/Oct/23  Resolved: 09/Feb/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: 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
depends on WT-10116 Return 0 timestamp for all_durable up... Closed
Related
is related to SERVER-71145 Allow observed all_durable to move ba... Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2023-02-20
Participants:

 Description   

In the AllDurableTimestamp unit test, we open a transaction at Timestamp(5, 1) but do not commit it yet. Then we fetch the all_durable timestamp and expect it to be Timestamp(5, 1). However, all_durable should not be Timestamp(5, 1) yet because the transaction has not committed.



 Comments   
Comment by Githook User [ 09/Feb/23 ]

Author:

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

Message: SERVER-71148 Re-enable assertion in `AllDurableTimestamp` test
Branch: master
https://github.com/mongodb/mongo/commit/467980502d5649fbc0d553aeb53646617b063e92

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