Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0, 8.0.0-rc5
Affects 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:

v8.0, v7.3
Sprint:
Service Arch 2024-05-13
Linked BF Score:
146
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

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

Assignee:: Ronald Steinke
Reporter:: Eric Milkie
Participants:: Eric Milkie, Githook User, Lauren Lewis, Ronald Steinke
Votes:: 7 Vote for this issue
Watchers:: 17 Start watching this issue

Created:: May 08 2017 03:10:11 PM UTC
Updated:: May 13 2024 01:51:46 PM UTC
Resolved:: Apr 30 2024 07:22:38 PM UTC
Confidence Status Last Update:: 02/Jul/23 12:29 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates