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

clean up log messages

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Minor - P4
    • Resolution: Fixed
    • 2.0.1
    • 2.7.4
    • Logging
    • Server 2.7.4

    Description

      We need to clean up our log messages. We generate a lot of noise because many log messages are not actionable, and don't mean anything – they appear to have been put in for original development and debugging, and left there. One example I get asked about a lot is the warning about being unable to release a recursive lock from a mapreduce.

      Attachments

        Issue Links

          is duplicated by

          New Feature - A new feature of the product, which has yet to be developed. SERVER-5092 Better named logging with tracing

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-13922 remove dbtemprelease

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-3989 Cannot suppress ClientCursor::yield "warnings" from logs

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-4780 Improve Memory Leak Warning Message

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              benety.goh@mongodb.com Benety Goh
              dan@mongodb.com Daniel Pasette (Inactive)
              Votes:
              16 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: