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

Initial sync could fail under replsetprio1.js settings

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.21, 3.6.13, 4.0.10
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0, v3.6, v3.4
    • Sprint:
      Repl 2019-04-22
    • Linked BF Score:
      22

      Description

      Initial sync doesn't survive sync source's state transitions in 4.0 or older. Under this test's settings, I think it is always possible for a node to step down while another node is still syncing from it. This is because when at least two nodes are available, primary could step down if the other node has higher priority. And if the third node is still in initial sync, then the initial sync will fail. A potential fix would be to set a higher numInitialSyncAttempts (currently set to 1) for this test. And I think this could happen with PV1 too.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: