[SERVER-32104] remove oldest_timestamp invariant check Created: 28/Nov/17  Updated: 30/Oct/23  Resolved: 28/Nov/17

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.6.0-rc7

Type: Task Priority: Major - P3
Reporter: Eric Milkie Assignee: Eric Milkie
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
Sprint: Storage 2017-12-04
Participants:
Linked BF Score: 0

 Description   

The oldest_timestamp invariant check was recently added to ensure that the oldest_timestamp always moves forward. In the old code, if it did not move forward, the out-of-order oldest_timestamp value was ignored. This could potentially cause the process to crash if mongod attempted to perform writes at a timestamp less than the latest oldest_timestamp, but I have yet to see any such crashes.



 Comments   
Comment by Githook User [ 28/Nov/17 ]

Author:

{'name': 'Eric Milkie', 'username': 'milkie', 'email': 'milkie@10gen.com'}

Message: SERVER-32104 remove failing invariant for 3.6
Branch: v3.6
https://github.com/mongodb/mongo/commit/e766422106fa6abfffeba20bc9d3a406d15301b1

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