[SERVER-6697] Determine correct ranges for priority in replicaSet configuration Created: 02/Aug/12 Updated: 10/Dec/14 Resolved: 02/Jun/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.2.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | elections | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
In ReplSetConfig::MemberCfg::check:
Note that the docs says priority is 0 <= x <= 1000, which contradicts the uassert above. |
| Comments |
| Comment by Matt Dannenberg [ 02/Jun/14 ] |
|
The problem has now flipped. All the checks in the code base seem to be between 0 and 1000, but the docs claim between it's 0 and 100.0. Filing a docs ticket. |