-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Fully Compatible
-
v8.1, v8.0, v7.0
-
Repl 2025-05-12, Repl 2025-05-26, Repl 2025-06-09, Repl 2025-06-23, Repl 2025-07-07, Repl 2025-07-21
-
200
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The proposed solution for SERVER-84734 is to remove the size validation inside the BSONObj constructor that checks that any BSON object is below the internal limit of 16MB+16KB, and check that it is less than the Buffer Max Limit of 125 MB instead. There are currently several tests across the server that will fail as a result of this change, as they rely on the implicit size check within the constructor
The code paths being checked in these tests need to be updated to do their own size validation if necessary before/alongside the change is made for SERVER-84734.
- blocks
-
SERVER-84734 Oplog entries can come close to 16 MB + 16 KB size
-
- Closed
-
- is related to
-
SERVER-84734 Oplog entries can come close to 16 MB + 16 KB size
-
- Closed
-
-
SERVER-108195 Audit write paths to ensure 16MB document size is being enforced explicitly and consistently
-
- Needs Scheduling
-
- related to
-
SERVER-107711 Increase benchmarks_sep thresholds
-
- Closed
-
-
SERVER-108196 Audit write paths to ensure 16MB document size is being enforced explicitly and consistently
-
- Needs Scheduling
-
-
SERVER-108263 Audit write paths to ensure 16MB document size is being enforced explicitly and consistently
-
- Needs Scheduling
-
-
SERVER-108269 Audit write paths to ensure 16MB document size is being enforced explicitly and consistently
-
- Needs Scheduling
-