[SERVER-44406] Add $backupCursor API to forcefully disable incremental backups Created: 04/Nov/19 Updated: 29/Oct/23 Resolved: 13/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.4, 4.3.3 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.2
|
||||
| Sprint: | Execution Team 2020-01-13, Execution Team 2019-12-30 | ||||
| Participants: | |||||
| Description |
|
Doing incremental backups against a node consumes resources to track blocks that have changed since the last backup. In the interest of safety, we will expose a command that can turn off the storage of incremental history (as an alternative to restarting the node). The backup application is still in complete control of which nodes are keeping incremental history. This ticket will not introduce a MongoDB "timeout" that turns off incremental history. |
| Comments |
| Comment by Githook User [ 25/Feb/20 ] |
|
Author: {'username': 'GWlodarek', 'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com'}Message: (cherry picked from commit 2cce9ab01cd9b4c19f643fdf942930538be59686) |
| Comment by Githook User [ 25/Feb/20 ] |
|
Author: {'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}Message: (cherry picked from commit 936b4dbc75574b090970db2d43baf397e569865f) |
| Comment by Githook User [ 13/Jan/20 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Githook User [ 13/Jan/20 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |