[SERVER-35747] Check supportsRecoverToStableTimestamp before calling getLastStableCheckpointTimestamp Created: 22/Jun/18  Updated: 29/Oct/23  Resolved: 25/Jun/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.1

Type: Task Priority: Major - P3
Reporter: Maria van Keulen Assignee: Maria van Keulen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-34606 Test (and possibly fix) behavior arou... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-07-02
Participants:
Linked BF Score: 0

 Description   

The looping logic of oplog truncation was shortened as part of SERVER-34606 by checking whether it is safe to truncate the oplog earlier on in the nested loops than previously. supportsRecoverToStableTimestamp should be called prior to the getLastStableCheckpointTimestamp call that was added as part of SERVER-34606.



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

Author:

{'name': 'Maria van Keulen', 'email': 'maria@mongodb.com', 'username': 'mvankeulen94'}

Message: SERVER-34606 Early return from majority commit point oplog truncation

(cherry picked from commit c1803e01a3827072b7dcd962a864c62a426824b6)

SERVER-35747 Don't check for timestamps on non timestamp supported SEs

(cherry picked from commit b7ff5816f4d9d468b1875013384e7e51184628a0)
Branch: v4.0
https://github.com/mongodb/mongo/commit/263055e76e41fc4c65dc3fbcaa59ec3a7eedbdcc

Comment by Githook User [ 25/Jun/18 ]

Author:

{'username': 'mvankeulen94', 'name': 'Maria van Keulen', 'email': 'maria@mongodb.com'}

Message: SERVER-35747 Don't check for timestamps on non timestamp supported SEs
Branch: master
https://github.com/mongodb/mongo/commit/b7ff5816f4d9d468b1875013384e7e51184628a0

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