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

    • Type: Icon: Question Question
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      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?

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

              Created:
              Updated:
              Resolved: