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

Revisit log levels for new migration protocol

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.4
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2020-03-09

    Description

      It's helpful to have log level 0 for the new components we're adding for a little while to aid in debugging test failures in evergreen but we should more carefully decide which to keep at level 0 and which to decrease.

      Also, we should decide whether to use the thread name as an identifier for log lines from range deletion code, or whether to introduce a new log component.

      Attachments

        Activity

          People

            alex.taskov@mongodb.com Alexander Taskov (Inactive)
            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: