-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 8.0 Required
-
Component/s: None
-
Query Execution
-
Fully Compatible
-
v8.0, v7.0
-
QE 2026-01-19, QE 2025-12-08
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Backporting SERVER-104405 (on 8.0 & 7.0) is too complex.
Instead, for 7.0 & 8.0 (and only those versions), introduce a new CursorResponseBsonSize limit of 16MB+32KB (either in general or limited specifically to oplog cursors).
This has the advantages of being simpler and the lowest risk solution, because:
- It shouldn't break any user writes.
- From the query side, the batch building code will stop adding new documents after we reach or exceed 16MB anyway.
- related to
-
SERVER-53387 Large internal metadata can trigger BSONObjectTooLarge for commands under the BSON size limit
-
- Backlog
-
-
SERVER-104405 Add explicit size validation where code is currently relying on BSONObj constructor
-
- Closed
-