[SERVER-17604] After abnormal ethernet or DoS attack failover to secondary expected Created: 16/Mar/15 Updated: 16/Mar/15 Resolved: 16/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Minor - P4 |
| Reporter: | Diego Scaravaggi | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hi All, I'm a newbie of Mongo, after setting up a replica set I notice that is primary machine is Alive (ping OK) but unresponsive on port 27017 an indefinite loop tentative without raising a new election of: 2015-03-16T15:47:17.568+0100 I REPL [ReplicationExecutor] Error in heartbeat request to vmdev2012next:27008; Location18915 Failed attempt to connect to vmdev2012next:27008; couldn't connect to server vmdev2012next:27008 (192.168.210.183), connection attempt failed |
| Comments |
| Comment by Diego Scaravaggi [ 16/Mar/15 ] |
|
Thanks a lot for your quick answer. I'll be search in google group and stackexchange. Thanks again |
| Comment by Ramon Fernandez Marina [ 16/Mar/15 ] |
|
dscaravaggi, looks like your replica set may be configured to listen in a different port, namely 27008 (instead of 27017), so I'd verify that. You may want to also check that there are no firewalls preventing the members from talking to each other. Please check the documentation on deploying a replica set for more information. Note also that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. Regards, |