Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-65703

Different time-series bucketing behavior depending on insert batch size

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • Execution Team 2022-06-13, Execution Team 2022-06-27
    • 55

      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.

            Assignee:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Reporter:
            henrik.edin@mongodb.com Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: