[SERVER-70021] Reevaluate time series bucket archival strategy Created: 27/Sep/22  Updated: 29/Oct/23  Resolved: 06/Oct/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Dan Larkin-York
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-10-17
Participants:
Linked BF Score: 120

 Description   

Currently we archive buckets under memory pressure or if we open a new bucket due to time forwards/backwards. We definitely want to continue to archive buckets under memory pressure, but we may wish to close buckets rather than archive them when we have time forwards/backwards.

If we keep these buckets eligible for query-based reopening, then we would retain good bucketing behavior in out-of-order scenarios, but we wouldn't track truly idle buckets as archived unnecessarily until we run into memory pressure.



 Comments   
Comment by Githook User [ 06/Oct/22 ]

Author:

{'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}

Message: SERVER-70021 Soft close time series buckets instead of archiving except under memory pressure
Branch: master
https://github.com/mongodb/mongo/commit/872b5054b7b434c22adcabfb990188eebb89090f

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