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

new 3.2 replica nodes "could not find member to sync from"

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Done
    • Icon: Minor - P4 Minor - P4
    • None
    • None
    • None
    • None

    Description

      It seems after completing the rolling upgrade from 3.0.12 to 3.2, the new nodes cannot sync with the primary instance for some reason. Do you know what could be causing this issue?

      Attachments

        Activity

          People

            kelsey.schubert@mongodb.com Kelsey Schubert
            eabott@synapsemail.com Enrique Abott
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: