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

Initial syncer should only connect to nodes in primary or secondary state

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.3
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Repl 2020-01-27

      Description

      Since due to SERVER-45610, we can successfully execute some reads of nodes in REMOVED, ROLLBACK, and RECOVERING states, to get a consistent initial sync we must ensure we never connect to such nodes in the first place.

      This ticket also ensures we do correct backoff when re-connecting (whether due to a node in the wrong state, or other reasons). And as a side effect it eliminates the ambiguity of the NotMasterOrSecondary error (which may be permanent due to a removed node, or temporary due to a restart); since we will never connect to a node a state other than PRIMARY or SECONDARY, we will never see that error.

      The testing for this is in SERVER-42705 and SERVER-45423.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              matthew.russotto Matthew Russotto
              Reporter:
              matthew.russotto Matthew Russotto
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: