[SERVER-29902] Roll Back to Checkpoint: Force a checkpoint after schemaVersion upgrade Created: 28/Jun/17 Updated: 27/Oct/23 Resolved: 03/Jul/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: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Comments |
| Comment by Spencer Brody (Inactive) [ 03/Jul/17 ] |
|
I think this is no longer necessary now that calling 'recoverToStableTimestamp' is going to force a checkpoint, and 'supportsRecoverToStableTimestamp' isn't going to return true until there's a valid timestamp that a checkpoint could be taken at. |