[SERVER-73605] Multi updates should limit memory usage to track updated RecordIds Created: 03/Feb/23  Updated: 07/Feb/23

Status: Blocked
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Arun Banala Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Query Execution
Participants:

 Description   

We currently keep track of the updated RecordIds in a hashmap. This could end up using huge amounts of memory if a multi:true update is modifying large number of documents. The is more problematic for clustered collections, given the size of the RecordIds for clustered collections can be much larger than a regular collection. We should spill to disk instead if the memory usage crosses certain threshold.


Generated at Thu Feb 08 06:25:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.