[SERVER-29109] Client metadata log message verbosity is not parallel with connection start/end messages - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Bug
Status: Open
Priority: Major - P3
Resolution: Unresolved
Affects Version/s: None
Fix Version/s: None
Component/s: Networking
Labels:
- sa-remove-fv-backlog-22

Assigned Teams:

Service Arch
Backwards Compatibility:
Minor Change
Operating System:
ALL
Backport Requested:

v7.1
Linked BF Score:
146

Description

One of the main behaviors of the --quiet command line switch is to suppress the "connection received" and "end connection" log messages. However, the new "received client metadata from" log message does not adhere to the --quiet switch. This means that users that used to be able to suppress a high volume of log messages from incoming connections no longer can do so.
We should either make --quiet not suppress all "connection" related messages, or we should make the "client metadata" messages be suppressed by --quiet.

Attachments

Issue Links

is duplicated by

SERVER-35564 The --quiet flag suppresses "connection accepted" messages but not "client metadata" messages

Closed

is related to

SERVER-37722 Quiet mode does not suppress connection end events

Closed

SERVER-43021 MongoS server crashes when attempt to update single record > 16MB (16793648)

Closed

related to

SERVER-35399 MongoDB Server not received client metadata

Closed

Activity

People

Assignee:: Tyler Brock

Reporter:: Eric Milkie

Participants:: Eric Milkie, Githook User, Lauren Lewis, Tyler Brock

Votes:: 7 Vote for this issue

Watchers:: 15 Start watching this issue

Dates

Created:: May 08 2017 03:10:11 PM UTC

Updated:: Aug 29 2023 10:23:38 PM UTC