[SERVER-86085] Improve naming/semantics around frozen time-series buckets and reopening Created: 01/Feb/24  Updated: 02/Feb/24

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

Type: Improvement Priority: Major - P3
Reporter: Gregory Noma 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
related to SERVER-80653 Retry when time-series bucket compres... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

The timeseries::bucket_catalog::conflictsWithReopening function does not return true for frozen buckets even though logically they do conflict with reopening. The reason that it doesn't return true in this case is because its callers often use it to determine whether to return a write conflict, but a write conflict is not the correct action for a frozen bucket because its state will never change. We may want to adjust the naming/function usage here in order to improve the semantics.


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