[SERVER-64186] Evaluate doing batched capped deletes in CollectionImpl::_cappedDeleteAsNeeded Created: 03/Mar/22  Updated: 26/Apr/23

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

Type: Task Priority: Major - P3
Reporter: Fausto Leyva (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-1864 Support Resizing Capped Collections Closed
is related to SERVER-34559 Explore options for capped collection... Backlog
Assigned Teams:
Storage Execution
Participants:

 Description   

Currently, deleting documents in '_cappedDeleteAsNeeded' happens in one transaction. As a result of SERVER-1864, this could be costly in the case where the newly set cappedSize decreases past the collections current size.

SERVER-1864 holds off on deleting documents until the next insert into the collection. After inserting, we check if deletions are needed and delete documents until the total size < cappedSize in one transaction. 


Generated at Thu Feb 08 05:59:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.