[SERVER-84680] Update numBucketsOpenedDueToMetadata logic, stats changed by multiple open metadata Created: 09/Jan/24  Updated: 05/Feb/24  Resolved: 05/Feb/24

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

Type: Task Priority: Major - P3
Reporter: Damian Wasilewicz Assignee: Damian Wasilewicz
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-86221 Complete TODO listed in SERVER-84680 Open
Participants:

 Description   

Once SERVER-79479 is merged in, the logic for marking a bucket as having been opened because its metadata was different than an incoming measurement will improperly identify buckets that are allocated in useBucket because no current open buckets have a proper time range for an incoming measurement, as having been opened because of metadata. This ticket would ensure that when we are actually adding multiple open buckets per metadata this does not cause bugs because of the statistic being off.

 

As part of this ticket we should also update stat logic (numBucketsArchivedDueToTimeForward, new stat for buckets opened due to hitting the max number of buckets allowed per metadata)



 Comments   
Comment by Gregory Wlodarek [ 05/Feb/24 ]

We're dropping the property that compressed buckets are sorted by time. So we no longer need to support multiple open buckets per metadata. Closing as won't do.

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