[SERVER-79480] Insert measurements into the best-fitting bucket when there are multiple open buckets per metadata Created: 28/Jul/23 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: | Gregory Wlodarek | 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: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Sprint: | Execution Team 2023-12-25, Execution Team 2024-01-08, Execution Team 2024-01-22, Execution Team 2024-02-05, Execution Team 2024-02-19 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
For a new measurement, the following bucket criteria must be met to consider inserting the measurement into it:
This can return multiple eligible buckets. We pick the bucket where the time difference is the smallest between the new measurement's timestamp and the last measurement's timestamp in each eligible bucket. This approach will minimize the number of open buckets 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. |