[SERVER-65703] Different time-series bucketing behavior depending on insert batch size Created: 15/Apr/22  Updated: 29/Oct/23  Resolved: 13/Jun/22

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

Type: Task Priority: Major - P3
Reporter: Henrik Edin Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Related
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-06-13, Execution Team 2022-06-27
Participants:
Linked BF Score: 55

 Description   

When calculating space usage for new fields in time-series inserts we don't take into account that fields are repeated in time-series buckets due to the control min/max fields.
https://github.com/mongodb/mongo/blob/2d46c87afcdf34a384d10e37b7b9b6ca2986fdf4/src/mongo/db/timeseries/bucket_catalog.cpp#L316-L322

This seems to be causing differences in how many measurements we can store in a single bucket depending on which batch size is used during insert.



 Comments   
Comment by Githook User [ 13/Jun/22 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-65703 Approximate control.min and control.max space usage for time-series inserts
Branch: master
https://github.com/mongodb/mongo/commit/6ebd2850069b676b7fa51a6e139d596d57ba94cd

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