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

Make all logs for query sampling go under the kSharding component

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible

    Description

      The logs for the QueryAnalysis{Sampler,Writer,Coordinator} are currently categorized under the kDefault component because strictly speaking query sampling can be used separately from the analyzeShardKey command. However, this has made debugging quite cumbersome since to see the level 1+ log messages, we need to increase the default log verbosity which includes all other components. Making the log messages go under the kSharding would allow us to see the messages by increasing just the log verbosity for the kSharding component.

      Attachments

        Activity

          People

            cheahuychou.mao@mongodb.com Cheahuychou Mao
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: