Mongo primary could not resolve secondary host name automatically after loosing connection for one time

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Networking, Replication
    • None
    • ALL
    • Hide
      1. Connection was lost between Primary and secondary.
      2. Restart was taken on secondary.
      3. Secondary state was secondary from rs.status().
      4. Primary rs.status still shows secondary not reachable.
      5. Primary server was step down.
      6. Secondary became primary rs.printSlaveReplicationInfo shows 2 second delay.
      7. New primary step down.
      8. Everything fine now.
      Show
      Connection was lost between Primary and secondary. Restart was taken on secondary. Secondary state was secondary from rs.status(). Primary rs.status still shows secondary not reachable. Primary server was step down. Secondary became primary rs.printSlaveReplicationInfo shows 2 second delay. New primary step down. Everything fine now.
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      HI,
      I am looking at strange issue in My sharded set up that could be some error also.
      As for some reason my secondary server was down it was taken a restart.
      After Restart my Primary keep giving error that secondary host name cant be resolved.
      I checked connection between both Primary and secondary and ping was successful and even i was able to connect Secondaries mongo with same host name from Primary.
      The issue was resolve only when i step down primary and then step it up again and issue was resolve.
      I am sure Primary should have taken it automatically when ever secondary was up and i should not need this manual process.
      In logs there was no error except heartbeat issue from primary to secondary.
      Thanks
      Virendra Agarwal

            Assignee:
            Kelsey Schubert
            Reporter:
            virendra agarwal
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: