[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: |
|
||||||||
| 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. 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: |