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

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.1, 4.7.0, 4.2.16
    • Affects Version/s: 4.0.12
    • Component/s: Replication
    • None
    • Fully Compatible
    • v4.4, v4.2, v4.0, v3.6
    • Repl 2020-05-18
    • 6

      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.

            Assignee:
            samy.lanka@mongodb.com Samyukta Lanka
            Reporter:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: