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

Include resolved IP address in rs.status()

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • Service Arch 2019-04-22

    Description

      Original title: Include resolved IP address in rs.status() and rs.conf()

      We often have to troubleshoot replication issues. It would be handy to include the IP address the DNS entry resolves to (from the MongoDB perspective) to help with diagnostics.

      For example

      2016-07-25T09:02:19.834-0400 I NETWORK  [ReplExecNetThread-49255] Socket closed remotely, no longer connected (idle 6 secs, remote host 10.71.219.130:27017)
      		 
      2016-07-25T09:02:19.879-0400 W NETWORK  [ReplExecNetThread-49255] Failed to connect to 10.71.219.130:27017, reason: errno:111 Connection refused

      I'd like to more easily associate these with a node. Alternatively, perhaps include the host in the logging? Or both?

      Attachments

        Issue Links

          is documented by

          Task - A task that needs to be done. DOCS-12658 Docs for SERVER-25284: Include resolved IP address in rs.status()

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Task - A task that needs to be done. SERVER-45304 Include resolved IP address in rs.status()

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-45270 Increased vulnerability to slow DNS

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              jesse@mongodb.com A. Jesse Jiryu Davis
              shakir.sadikali@mongodb.com Shakir Sadikali
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: