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

Avoid throttling replica set elections

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.11
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • Storage NYC 2019-04-22, Storage NYC 2019-05-06

      Determine whether it is possible to isolate lock acquisitions performed by system operations in order to avoid unnecessarily throttling these lock acquisitions. If it is possible, implement these isolations.
      At minimum, this ticket should make sure that throttling of writes doesn't impact replica set elections and that secondary oplog application writes do not get throttled. The work for this ticket also should include verifying that the serverStatus command is not throttled.
      This ticket should also provide a framework to exclude operations from being throttled. One strategy for implementing this is to add a flag to the OperationContext that represents whether this operation should be throttled. Particular operations that are found to be inappropriate for throttling can set this flag so the mechanism can exclude them.
      A check should be added here that our replication state is not primary. This handling will avoid throttling operations on secondaries.

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

              Created:
              Updated:
              Resolved: