[SERVER-4003] If only one node in set go straight to PRIMARY status Created: 03/Oct/11  Updated: 16/May/13  Resolved: 16/May/13

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

Type: Improvement Priority: Major - P3
Reporter: Mathias Stearn Assignee: Unassigned
Resolution: Duplicate Votes: 9
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Participants:

 Description   

Currently it goes to SECONDARY and takes a while before electing self even though there is no-one to contest the election.

This is especially annoying when doing the following steps to bring up a new node:

rs.initiate()
rs.add(getHostName()+':10002')
rs.add(getHostName()+':10003')

I have to wait ~30 seconds before running the second line because the first and only node takes a long time to elect itself.



 Comments   
Comment by Eric Milkie [ 16/May/13 ]

This was fixed by SERVER-4836. It takes me about 1 second after issuing rs.initiate() to have the single node transition to PRIMARY state (assuming data files are already preallocated).

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