Revisit log levels for new migration protocol

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2020-03-09
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Alexander Taskov (Inactive)
            Reporter:
            Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: