fix: suppress MongoDB connection logs to prevent memory leak #15790
+6
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #15785
Addresses memory leak caused by excessive MongoDB connection logs when connecting without authentication.
Adds
mongodbLogComponentSeveritiesconfiguration to suppress client-side connection pool logs.Changes
mongodbLogComponentSeveritiesoption in lib/drivers/node-mongodb-native/connection.js'off'by defaulthasUserDefinedPropertycheck to respect user overridesTechnical Details
Note
This addresses client-side logging. If server-side MongoDB logs continue to accumulate, server logging configuration may need adjustment.
Testing