[SERVER-30594] Roll Back to Checkpoint: inform storage engine to take unstable checkpoints in master-slave Created: 10/Aug/17  Updated: 27/Oct/23  Resolved: 27/Nov/17

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

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Backlog - Replication Team
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Participants:

 Comments   
Comment by Eric Milkie [ 15/Nov/17 ]

I suppose not! We should close all the master/slave tickets in the backlog at once rather than doing them piecemeal, I think.

Comment by Judah Schvimer [ 15/Nov/17 ]

milkie, Is there any further work to be done on this ticket, since master-slave is being removed in 3.8?

Comment by Eric Milkie [ 02/Nov/17 ]

In order to get WiredTiger to clean up old timestamp data, I ended up calling setStableTimestamp() as part of SERVER-31797

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