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

Revisit log levels for new migration protocol

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 4.3 Desired
    • Component/s: Sharding
    • Labels:
      None

      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

            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: