[SERVER-24100] Mongo primary could not resolve secondary host name automatically after loosing connection for one time Created: 09/May/16  Updated: 08/Jan/24  Resolved: 17/May/16

Status: Closed
Project: Core Server
Component/s: Networking, Replication
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: virendra agarwal Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:
  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.
Participants:

 Description   

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



 Comments   
Comment by Kelsey Schubert [ 17/May/16 ]

Hi agarwal.viren@gmail.com,

Thanks for your report. This is likely a network-related issue, however you may be affected by SERVER-24058. Therefore, I would recommend upgrading to MongoDB 3.2.7 when it is released and checking if the issue persists.

Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group.

Kind regards,
Thomas

Generated at Thu Feb 08 04:05:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.