[DOCS-7227] Replica Set Arbiter Priority defaulted to 1 Created: 22/Feb/16 Updated: 15/Aug/17 Resolved: 15/Aug/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | mongodb-3.0 |
| Fix Version/s: | 3.5.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mrityunjay Sharma | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | arbiter, priority, replicaset | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 6 years, 26 weeks, 1 day ago | ||||||||
| Epic Link: | DOCS: 3.6 Server | ||||||||
| Description |
|
In Replica Set Priority Documentation of 3.0, at https://docs.mongodb.org/v3.0/tutorial/adjust-replica-set-member-priority/ it is mentioned, "To block a member from seeking election as primary, assign it a priority of 0. Hidden members, delayed members, and arbiters all have priority set to 0.". However, I have found that in the server with default config, arbiter default priority is set to 1. See following. Either the documentation or the server code needs to be changed. It should be 0 for practical purposes. { |
| Comments |
| Comment by Githook User [ 15/Aug/17 ] |
|
Author: {'username': 'kay-kim', 'email': 'kay.kim@10gen.com', 'name': 'kay'}Message: |
| Comment by Githook User [ 10/Mar/16 ] |
|
Author: {u'username': u'rkumar-mongo', u'name': u'ravind', u'email': u'ravind.kumar@10gen.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 10/Mar/16 ] |
|
Author: {u'username': u'rkumar-mongo', u'name': u'ravind', u'email': u'ravind.kumar@10gen.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Ravind Kumar (Inactive) [ 09/Mar/16 ] |