[SERVER-16631] Strange downgrade behavior in large mixed replica sets (2.6/2.8) Created: 22/Dec/14 Updated: 22/Dec/14 Resolved: 22/Dec/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | 28qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
If you start with >12 2.8 nodes, and downgrade one node to 2.6, it just works. No logged errors, no complaints, just becomes a secondary. Then, this is the weird part: if you give that 2.6 node a higher priority to make it primary, all 13 nodes go into state SECONDARY, and the 2.6 node starts logging an invalid config. |