[SERVER-19491] arbiters should have priority 0 for clarity Created: 20/Jul/15 Updated: 06/Dec/17 Resolved: 16/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Matthew Russotto |
| Resolution: | Done | Votes: | 1 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Repl 2017-02-13, Repl 2017-03-06 | ||||||||
| Participants: | |||||||||
| Description |
|
Right now they have priority 1 (which is ignored by the election code). |
| Comments |
| Comment by Githook User [ 16/Feb/17 ] |
|
Author: {u'username': u'mtrussotto', u'name': u'Matthew Russotto', u'email': u'matthew.russotto@10gen.com'}Message: Configurations with arbiters having priority 1 will be silently changed to 0. |
| Comment by Matthew Russotto [ 13/Feb/17 ] |
|
Code review url: https://mongodbcr.appspot.com/116570001/ |
| Comment by Spencer Brody (Inactive) [ 03/Feb/17 ] |
|
I think replSetInitiate/replSetReconfig should error if priority for an arbiter is set to anything other than 1 or 0, and if it's 1, automatically convert it to 0 (to account for backwards compatibility with old configs where the default was 1). |