[SERVER-21939] Ability to force a checkpoint and keep it around for a given amount of time Created: 18/Dec/15 Updated: 06/Dec/22 Resolved: 09/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Daniel Coupal | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
Due to the ability to have checkpoints that are immutable with WiredTiger, MongoDB could create checkpoints at a given point in time. A checkpoint would be created by each replica of a replica set at the same point in time. It would allow to run operations or scripts to compare data, while the database instance is still accepting writes. |
| Comments |
| Comment by Connie Chen [ 09/Nov/20 ] |
|
Durable History should allow reads at a specific point in time for cluster wide snapshot reads |