[SERVER-23363] ReplicaSet heartbeat requests failing to connect Created: 26/Mar/16 Updated: 28/Mar/16 Resolved: 28/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.2.0 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Minor - P4 |
| Reporter: | Krishnan Kannan | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
I have setup a replica set with 2 members and 1 arbiter. In the following log, 016-03-26T23:37:03.977+0000 I REPL [ReplicationExecutor] Error in heartbeat request to mercury:27017; Location18915 Failed attempt to connect to mercury:27017; couldn't connect to server mercury:27017 (10.x.x.x), connection attempt failed |
| Comments |
| Comment by Kelsey Schubert [ 28/Mar/16 ] |
|
Hi kxkannan, Thank you for the follow up. Since you were able to resolve this issue, I will be closing this ticket. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. Kind regards, |
| Comment by Krishnan Kannan [ 27/Mar/16 ] |
|
This was due to each of the mongodb instance listening only on 127.0.0.1. I changed the bindIp to listen on the internal IP address and the connections between the mongo instances started working fine. |