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

logging cleanup: review severity of sharding log messages

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding
    • Server 2.7.4, Server 2.7.5, Server 2.7.6

      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"

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            andre.defrere@mongodb.com Andre de Frere
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: