[SERVER-38290] Set oldest timestamp to recovery timestamp when started with recoverFromOplogAsStandalone Created: 28/Nov/18 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Danny Hatcher (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Participants: | |||||
| Description |
|
When using the recoverFromOplogAsStandalone flag, checkpoints can be performed multiple times on the same data. As the node is not a member of a replica set at the time and is in read-only mode, moving the oldest timestamp forward should reduce the amount of unnecessary recovery work. |