Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Storage
Labels:
None

Assigned Teams:

Storage Execution
Backwards Compatibility:
Fully Compatible
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

Once MongoDB switches to journaling only the oplog, it will be necessary to ensure that the oplog is not truncated to a point in time that is after the last completed checkpoint.

MongoDB should track the timestamp for the last completed checkpoint, and ensure that oplog truncate doesn't remove any content newer than that point in time.

depends on

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

Closed

duplicates

SERVER-30460 Grow the oplog when the replication commit point falls behind the back of where it would normally be truncated to

Closed

Assignee:: [DO NOT USE] Backlog - Storage Execution Team
Reporter:: Alexander Gorrod
Participants:: [DO NOT USE] Backlog - Storage Execution Team, Alexander Gorrod, Daniel Gottlieb, Spencer Brody
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: May 15 2017 06:54:56 PM UTC
Updated:: Dec 06 2022 04:01:05 AM UTC
Resolved:: Aug 01 2017 06:51:44 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates