Large internal metadata can trigger BSONObjectTooLarge for commands under the BSON size limit

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • ALL
    • N&O Prioritized List, QE 2025-02-03
    • 3
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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).

            Assignee:
            Unassigned
            Reporter:
            Jack Mulrow
            Votes:
            9 Vote for this issue
            Watchers:
            65 Start watching this issue

              Created:
              Updated: