[SERVER-30309] Have WiredTigerKVEngine implement StorageEngine::supportsRecoverToStableTimestamp Created: 25/Jul/17  Updated: 30/Oct/23  Resolved: 03/Aug/17

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

Type: Task Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-29891 Roll Back to Checkpoint: Call setStab... Closed
depends on SERVER-30184 Roll Back to Checkpoint: Call setInit... Closed
depends on SERVER-30185 Roll Back to Checkpoint: Call setInit... Closed
depends on SERVER-30335 Roll Back to Checkpoint: Call setInit... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage 2017-07-31, Storage 2017-08-21
Participants:

 Description   

As replication provides updates values for the "stable timestamp" and "initial data timestamp", storage needs to respond appropriately to whether it has a history that covers the necessary window.



 Comments   
Comment by Githook User [ 10/Aug/17 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com'}

Message: SERVER-30309: Stage changes for supportsRecoverToStableTimestamp
Branch: master
https://github.com/mongodb/mongo/commit/4cfb89fa0ed61b6ea8f63a1452561cd95ffe0626

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