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

logging cleanup: review severity of sharding log messages

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • None
    • None
    • Sharding
    • Sharding
    • Server 2.7.4, Server 2.7.5, Server 2.7.6

    Description

      Some log messages to do with sharding are too verbose. These fill the logs and don't make much sense to the end user, as the internals of shard versions etc are not known. Increasing their logging level will clean up the logs and prevent misattributed issues.

      Messages such as "could not initialize cursor across all shards because : stale config detected for ns"

      Attachments

        Issue Links

          depends on

          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

          Task - A task that needs to be done. DOCS-1019 More detailed documentation on Sharding Internals

          • 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-30841 Lower the amount of metadata refresh logging

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

          Activity

            People

              backlog-server-sharding Backlog - Sharding Team
              andre.defrere@mongodb.com Andre de Frere
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: