[SERVER-37054] Make sure the snapshot read timestamp is not older than the oldest available timestamp in prepare_conflict_read_concern_behavior.js Created: 07/Sep/18  Updated: 29/Oct/23  Resolved: 13/Sep/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.1.3

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2018-09-24
Participants:
Linked BF Score: 12

 Description   

Sometimes it can become older than the oldest available timestamp and cause a SnapshotTooOld error



 Comments   
Comment by Githook User [ 13/Sep/18 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}

Message: SERVER-37054 Turn off timestamp reaping to prevent the oldest timestsamp from advancing in prepare_conflict_read_concern_behavior.js
Branch: master
https://github.com/mongodb/mongo/commit/ba14a58e71334dda6babb92e89c7ce784f30120f

Comment by Githook User [ 12/Sep/18 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}

Message: SERVER-37054 Make sure snapshot read timestamp is not older than the oldest available timestamp in prepare_conflict_read_behavior.js
Branch: master
https://github.com/mongodb/mongo/commit/96cbd0c40f585fa7b4b8d3aa92ca63a6dce63b7b

Comment by Githook User [ 12/Sep/18 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}

Message: SERVER-37054 Make sure snapshot read timestamp is not older than the oldest available timestamp in prepare_conflict_read_behavior.js
Branch: master
https://github.com/mongodb/mongo/commit/96cbd0c40f585fa7b4b8d3aa92ca63a6dce63b7b

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