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

Majority committed replication lag spikes after an election

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      ALL
    • Sprint:
      Repl 2019-10-21, Repl 2019-11-04, Repl 2019-11-18

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: