[SERVER-16630] Inconsistent behavior in large replica sets mixing 2.6 and 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
related to SERVER-16631 Strange downgrade behavior in large m... Closed
Operating System: ALL
Participants:

 Description   

You get different behavior from 2.6 nodes in >12 node replica sets depending on how they got there. If you start with >= 12 nodes in a 2.8 replica set, then add a 2.6 node, it will be in the UNKNOWN state, logging an invalid config. If you instead start with 12 2.6 nodes, then upgrade a node to 2.8 and make it the primary, then add an additional 2.8 node (making 13 total), the 2.6 nodes will log the invalid config, but stay in the SECONDARY state.


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