[SERVER-63039] Add a staged document size target to BatchedDeleteStage Created: 27/Jan/22 Updated: 29/Oct/23 Resolved: 13/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Josef Ahmad | Assignee: | Josef Ahmad |
| 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 2022-04-18 | ||||||||
| Participants: | |||||||||
| Description |
|
Stage document deletions up to a targetStagedDocBytes batch parameter to put an upper bound to the memory footprint. |
| Comments |
| Comment by Githook User [ 13/Apr/22 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: |
| Comment by Haley Connelly [ 06/Apr/22 ] |
|
We are considering repurposing this ticket to limit the approximate bytes of documents staged in the buffer. We need to limit the amount of data buffered in memory after changes from |