[SERVER-46076] Stream incremental backup data Created: 11/Feb/20 Updated: 29/Oct/23 Resolved: 08/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | James Heppenstall |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Execution Team 2020-05-04, Execution Team 2020-05-18 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Prior to incremental WT backups, MongoDB would copy all of the filenames from WT into memory and return them over the wire as needed. This wasn't particularly costly because internally, WT would already keep all filenames in memory. Now with incremental backups, WT streams the filename/block information from an underlying table. There would be gains (in terms of reduced working set memory) if MongoDB advanced the WT cursor as the external request needs more documents. |
| Comments |
| Comment by Githook User [ 08/May/20 ] |
|
Author: {'name': 'Jamie Heppenstall', 'email': 'jamie.heppenstall@mongodb.com', 'username': 'JamesHeppenstall'}Message: |
| Comment by Githook User [ 08/May/20 ] |
|
Author: {'name': 'Jamie Heppenstall', 'email': 'jamie.heppenstall@mongodb.com', 'username': 'JamesHeppenstall'}Message: |