-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Service Arch
-
ALL
-
(copied to CRM)
-
3
Before an internal request is sent, metadata may be added to it through registered hooks (e.g. $clusterTime, $audit). Eventually this metadata is combined with the request's command body into an op msg, which will fail with BSONObjectTooLarge if the combined size of the metadata and command body is over the BSONObjMaxInternalSize limit.
This is a problem for commands that are dynamically built within the server that can be near the size limit (like batch writes) because they don't currently account for the exact size of the metadata to be added, which can cause persistent BSONObjectTooLarge errors if the metadata is large enough, like with complicated LDAP roles (which leads to large $audit metadata).
- is related to
-
SERVER-77653 Batch write size estimation logic on mongos doesn't account for top-level command fields
- Open
-
SERVER-55062 Change stream events can exceed 16MB with no workaround
- Closed
-
SERVER-64592 Make sure events with large documentKey do not crash change stream
- Closed