[SERVER-1503] rs priorities other than 0 and 1 not supported yet Created: 28/Jul/10 Updated: 12/Jul/16 Resolved: 12/Apr/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 1.9.0 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 6 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
db version v1.5.7-pre-, pdfile version 4.5 |
||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
The member initializing the set always seems to be elected master, even if other members have higher priority. e.g., start three members on 27017, 27018, & 27019 and do: > rs.initiate({_id:"unicomplex", members:[{_id:0,host:"ubuntu:27017", priority:1}, {_id:1, host:"ubuntu:27018", priority:2}, {_id:2, host:"ubuntu:27019", priority:3}]}) then: > db.isMaster() |
| Comments |
| Comment by auto [ 12/Apr/11 ] |
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: rs priorities |
| Comment by Dwight Merriman [ 29/Jul/10 ] |
|
OK i have made the server complain about priorities other than zero and 1 for now. I will add support for other priorities asap but this way it at least does not promise to do things it doesn't. there's a good chance this can be in 1.6.0 but I want to make sure whatever goes out is solid even if something moves to 1.6.1. |
| Comment by Alex [ 29/Jul/10 ] |
|
Similar issue: 6 hosts, priorities 100,90,80,70,60,50. rs.stepDown() on the Master -> multiple times host3 with priority 80 becomes the next master skipping host2 with prio 90. rs.stepDown() on host3 will then elect host2 as the next master. |
| Comment by auto [ 28/Jul/10 ] |
|
Author: {'login': '', 'name': 'Kristina Chodorow', 'email': 'k@ubuntu.(none)'}Message: rs priority test |