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

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Done
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • 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
            Reporter:
            Enrique Abott
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: