-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
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.
- is depended on by
-
COMPASS-9926 Investigate changes in SERVER-108565: Check bucket size before writing for ordered time-series inserts
-
- Closed
-
-
TOOLS-3986 Investigate changes in SERVER-108565: Check bucket size before writing for ordered time-series inserts
-
- Closed
-
- is related to
-
SERVER-104405 Add explicit size validation where code is currently relying on BSONObj constructor
-
- Closed
-
-
TOOLS-3986 Investigate changes in SERVER-108565: Check bucket size before writing for ordered time-series inserts
-
- Closed
-
- related to
-
SERVER-103720 Unit test and rework interface to calculateBucketFieldsAndSizeChange
-
- In Progress
-
-
SERVER-112922 DeleteOne fails to remove oversized documents via time-series view
-
- Investigating
-