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

Increase isSelf logging verbosity

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.1, 4.7.0
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.4
    • Sprint:
      Repl 2020-06-29
    • Linked BF Score:
      14

      Description

      As a part of SERVER-48347, we added debug logging to the isSelf codepath to determine why isSelf could fail.

      However, after doing so, we noticed that other suites would also benefit from this logging. Since they are logged under the NETWORK component, we would have to increase the verbosity per suite (sometimes in reaction to seeing a failure we could not diagnose without extra isSelf logging).

      It could be useful to change these logs to warnings or log them at the default log level. Based on the conversation in BACKPORT-7368, we should investigate the risk of flooding the logs when a node is removed and it retries isSelf on every heartbeat. It could end up being too verbose.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              pavithra.vetriselvan Pavithra Vetriselvan
              Reporter:
              pavithra.vetriselvan Pavithra Vetriselvan
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: