[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: |
|
||||
| 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() 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 |