[SERVER-77334] LOGV2 messages may throw BSONObjectTooLarge exceptions Created: 19/May/23  Updated: 29/Oct/23  Resolved: 09/Jun/23

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Mark Benvenuto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Server Security
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Security 2023-06-12
Participants:

 Description   

It is possible for the log attributes when serialized using the custom serialize(), toBSON(), etc. members to trigger a BSONObjectTooLarge exception. Ideally the log line truncation performed by the logging subsystem would be performed at the same time to retain a portion of the log attributes rather than throwing an exception.

Worth considering would be whether the logging subsystem should swallow other exceptions thrown by the custom serialization functions.



 Comments   
Comment by Githook User [ 07/Jun/23 ]

Author:

{'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}

Message: SERVER-77334 LOGV2 messages may throw BSONObjectTooLarge exceptions
Branch: master
https://github.com/mongodb/mongo/commit/f5722950cfd626faad8926f87691496fbfe54695

Generated at Thu Feb 08 06:35:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.