Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-29109

Client metadata log message verbosity is not parallel with connection start/end messages

    XMLWordPrintable

    Details

    • Operating System:
      ALL

      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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-35564 The --quiet flag suppresses "connection accepted" messages but not "client metadata" messages

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-37722 Quiet mode does not suppress connection end events

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-43021 MongoS server crashes when attempt to update single record > 16MB (16793648)

          • Major - P3 - Major loss of function.
          • Investigating
          related to

          Question - SERVER-35399 MongoDB Server not received client metadata

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              • Votes:
                5 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated: