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

Disabled chaining should enforce sync source change when the primary steps down even if the oplog fetcher isn't killed on sync source

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 4.0.12
    • Fix Version/s: 4.4.1, 4.7.0
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.4, v4.2, v4.0, v3.6
    • Sprint:
      Repl 2020-05-18
    • Case:
    • Linked BF Score:
      6

      Description

      Since we no longer kill readers and close their connections on stepdown, the nodes syncing from the primary may not have a chance to choose a new sync source even if chaining is disabled.

      SERVER-21537 has similar symptoms when the heartbeats are stale. Both of them can be addressed in the Smart Chaining project.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              samy.lanka Samyukta Lanka
              Reporter:
              siyuan.zhou Siyuan Zhou
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: