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

logging cleanup: review severity of sharding log messages

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 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

        Activity

          People

            backlog-server-sharding [DO NOT USE] 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: