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

Majority committed replication lag spikes after an election

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • ALL
    • Repl 2019-10-21, Repl 2019-11-04, Repl 2019-11-18

      One of my scripts for testing Flow Control prompts an election. I've noticed that in some runs of the test, there is a spike in reported lastCommitted lag that occurs immediately after the election. This spike occurred both when the election chose the same primary as previously and when the election chose a different node as primary. Flow Control is a consumer of lastCommitted lag, so it will respond to the spike and throttle writes. I don't see why lastCommitted lag should have a reason to spike, particularly if the same primary is elected, so I believe this behavior should be investigated.

            Assignee:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Reporter:
            maria.vankeulen@mongodb.com Maria van Keulen
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: