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

A new server added to a Replica Set Fails to start Replication

XMLWordPrintableJSON

    • Type: Icon: Question Question
    • Resolution: Cannot Reproduce
    • Priority: Icon: Blocker - P1 Blocker - P1
    • None
    • Affects Version/s: 2.0.0, 2.2.2
    • Component/s: Replication
    • None
    • Environment:
      The Primary and ARB are 2.0.0 and the new Server is 2.2.2

      I have tried to start a 2.0.0 Secondary and failed to get the Replication started. Then I updated the Secondary to 2.2.2 and it also fails to replicate.

      What I see is that the OpTime for the Secondary is "stuck" at the time of the "backup". The steps from booting to Secondary look like they happen over time, then the server just never gets "caught up" to the OpTime of the Primary.

            Assignee:
            Unassigned Unassigned
            Reporter:
            mycloudwatcher Edward M. Goldberg
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: