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

Strange downgrade behavior in large mixed replica sets (2.6/2.8)

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • 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

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: