[SERVER-27292] replicaset Member failover time for mongodb v2.4.2 Created: 06/Dec/16 Updated: 09/Dec/16 Resolved: 06/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.2 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Omer Abdullah Bin Mahfooz | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
Hi, We have implemented a replica set which uses 2 nodes (say nodeA and nodeB) for data and another node for arbiter. Mongo version used is 2.4.2 on Centos 6 x64 The system takes around 30 seconds or more to failover and elect a Primary in case any one member which was Primary goes down. We have scenarios where the network can fluctuate and recover on its own. Is there a way to increase or decrease this failover detection time ? Any configuration parameters ? Thanks Omer |
| Comments |
| Comment by Kelsey Schubert [ 06/Dec/16 ] |
|
Hi omerabm, Thanks for your report. 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. Finally, I would strongly recommend upgrading to a newer version of MongoDB. MongoDB 2.4 and 2.6 are no longer supported. In MongoDB 3.2, we introduced a new replication protocol, which reduces failover time. To take advantage of this improvement as well as many others, please follow the recommended upgrade path to MongoDB 3.4. Kind regards, |