[SERVER-75176] Limit the memory usage during time-series updates Created: 23/Mar/23 Updated: 02/Nov/23 Resolved: 02/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Yuhong Zhang | Assignee: | Damian Wasilewicz |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Execution NAMR Team 2023-08-07, Execution NAMR Team 2023-09-18, Execution NAMR Team 2023-10-02, Execution NAMR Team 2023-10-16, Execution Team 2023-10-30, Execution Team 2023-11-13 | ||||
| Participants: | |||||
| Description |
|
Repurposing the ticket to add a memory limit (potentially 100MB) of the side bucket catalog used for each update command. We should return an error if an update exceeds the lmit. |
| Comments |
| Comment by Githook User [ 02/Nov/23 ] |
|
Author: {'name': 'Damian Wasilewicz', 'email': 'damian.wasilewicz@mongodb.com', 'username': 'DamianWasilewicz'}Message: |
| Comment by Yuhong Zhang [ 07/Apr/23 ] |
|
For the worst case the users could expand every single measurement in a full bucket that each new measurement will exceed the size limit. It will be rare and reasonable to disallow (at least as the first step). |
| Comment by Fausto Leyva (Inactive) [ 07/Apr/23 ] |
|
Just so I am understanding correctly, this ticket addresses the scenario where we update half of the measurements in a full bucket to measurement values 3 times their original size? I believe the expectation is that is will be unlikely and this ticket just aims to cover all our bases, does that sound about right? yuhong.zhang@mongodb.com |