Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.5.10
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2017-07-31
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

supportsRecoverToStableTimestamp(), setStableTimestamp(), setInitialDataTimestamp, and recoverToStableTimestamp().
This should just be a temporary implementation in db/storage/storage_engine.h, not pure-virtual so that we do not break any individual storage engines. The Storage Team will implement the function in all of the specific storage engines and then make it pure-virtual.

is depended on by

SERVER-29890 Roll Back to Checkpoint: check supportsRecoverToStableTimestamp() when deciding to use rollback to checkpoint algorithm

Closed

SERVER-29898 Roll Back to Checkpoint: Call recoverToStableTimestamp() under the global X lock

Closed

SERVER-30184 Roll Back to Checkpoint: Call setInitialDataTimestamp at the end of processing replSetInitiate

Closed

SERVER-30185 Roll Back to Checkpoint: Call setInitialDataTimestamp at the beginning and end of initial sync

Closed

Assignee:: Judah Schvimer
Reporter:: Judah Schvimer
Participants:: Githook User, Judah Schvimer
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Jun 28 2017 05:03:56 PM UTC
Updated:: Oct 30 2023 11:15:39 PM UTC
Resolved:: Jul 11 2017 02:54:55 PM UTC
Confidence Status Last Update:: 28/Jun/17 8:54 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates