[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:
Related
is related to SERVER-16630 Inconsistent behavior in large replic... Closed
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.


Generated at Thu Feb 08 03:41:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.