Check bucket size before writing to storage for time-series writes

XMLWordPrintableJSON

    • Storage Execution
    • Fully Compatible
    • v8.2, v8.0, v7.0
    • Storage Execution 2025-08-04, Storage Execution 2025-08-18, Storage Execution 2025-09-01, Storage Execution 2025-09-15, Storage Execution 2025-09-29, Storage Execution 2025-10-13
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Certain writes to time-series collections are able to generate documents larger than 16MB, which can crash secondaries. Various conservative size limits already exist that prevent most writes from getting close to the BSON 16 MB size limit. This ticket adds a final check to time-series bucket writes before writing to storage.

       

      Ordered writes will retry oversized bucket updates on a new bucket automatically, to try to fit the measurement in the collection as best as possible. All other writes ([un]ordered bucket insert and unordered update) will reject writes that are too big.

            Assignee:
            Matt Kneiser
            Reporter:
            Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: