[SERVER-1500] rs doesn't elect primary if initiated by an arbiter Created: 27/Jul/10 Updated: 12/Jul/16 Resolved: 29/Jul/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 1.5.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Dwight Merriman |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
That is, if db is connected to sf1:27017 and you set sf1:27017 to be arbiterOnly in replSetInitiate, the other machines will endlessly spin with: Tue Jul 27 18:33:43 [rs Manager] replSet info not trying to elect self, do not yet have a complete set of data from any point in time I started up: Then ran: test in replsetarb1.js |
| Comments |
| Comment by Dwight Merriman [ 29/Jul/10 ] |
|
resolved by disallowing. if you want, you can keep the test and make it verify that the initiate returns an error. |
| Comment by Alex [ 29/Jul/10 ] |
|
+1 |
| Comment by Che-Ching Wu [ 29/Jul/10 ] |
|
This works here. However, I've got this kind of message 'replSet info not trying to elect self, do not yet have a complete set of data from any point in time'. My commands are:
|
| Comment by auto [ 27/Jul/10 ] |
|
Author: {'login': '', 'name': 'Kristina Chodorow', 'email': 'k@ubuntu.(none)'}Message: failing rs test |