Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-16630

Inconsistent behavior in large replica sets mixing 2.6 and 2.8

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • ALL

    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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            charlie.swanson@mongodb.com Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: