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

Page on troubleshooting replica sets needs additional information

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None

    Description

      The page on troubleshooting Replica Sets needs additional information.

      Things to include are:

      1) Running 'rs.status()' on all nodes in the set to check the status of replication
      2) Running 'db.printReplicationInfo()' on all nodes in the set to check the size of the oplog
      3) Running 'db.printSlaveReplicationInfo()' on all nodes in the set to check the replication delay
      4) Using 'mongo' to test the connection from every node to every other node (both directions)

      Some notes about this last:

      • There must be connectivity from every node to every other node in order for replication to work
      • Problems with networking or firewall rules can prevent this connectivity, and hence prevent replication from working
      • Given that there are three nodes in the set, one node running on each of hosts A, B, and C, the process would be:
        • On host A:
          • Run "$ mongo --host B --port 27017"
          • Run "$ mongo --host C --port 27017"
        • Repeat the process on hosts B & C (each trying to connect to the other two hosts)
        • If any of the connections fails, there's a networking or firewall issue that needs to be diagnosed separately

      Attachments

        Activity

          People

            bgrabar Bob Grabar
            william.zola@10gen.com William Zola
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              11 years, 19 weeks, 6 days ago