Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
ALL
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.
Attachments
Issue Links
- is related to
-
SERVER-16630 Inconsistent behavior in large replica sets mixing 2.6 and 2.8
-
- Closed
-