Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-12658

Docs for SERVER-25284: Include resolved IP address in rs.status()

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.11
    • Component/s: manual, Server
    • Labels:

      Description

      Description

      Description:

      New "ip" field in each member subdocument within rs.status() / replSetGetStatus reply.

      Engineering Ticket 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?

      Scope of changes

      • rel notes
      • replSetGetStatus

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              kay.kim Kay Kim (Inactive)
              Participants:
              Last commenter:
              Kay Kim Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                2 years, 16 weeks, 1 day ago
                Date of 1st Reply: