Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Sprint:
Storage 2017-07-31, Storage 2017-08-21
Confidence Status:
None
Work Order:
3

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

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.

depends on

SERVER-29891 Roll Back to Checkpoint: Call setStableTimestamp() when commit point or last applied changes

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

SERVER-30335 Roll Back to Checkpoint: Call setInitialDataTimestamp at startup

Closed

Assignee:: Daniel Gottlieb (Inactive)
Reporter:: Daniel Gottlieb (Inactive)
Participants:: Daniel Gottlieb, Githook User
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Jul 25 2017 07:54:23 PM UTC
Updated:: Oct 30 2023 11:14:57 PM UTC
Resolved:: Aug 03 2017 01:13:20 AM UTC
Confidence Status Last Update:: 27/Jul/17 3:19 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates