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

Investigate and implement desired Flow Control throttling for multi-document transactions

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.6, 4.4.0-rc0
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4, v4.2
    • Sprint:
      Execution Team 2020-03-09, Execution Team 2020-03-23

      Description

      Multi-document transactions can be subject to Flow Control at prepare or commit time. However, by this point, the work and resources for the transaction have already been consumed, so further subjecting the transaction to Flow Control would prolong an already costly operation. The work for this ticket should be to investigate the appropriate means to avoid throttling prepare/commit/abort for transactions while still preventing new transactions from beginning when there is substantial replication lag.

      prepare/commit/abort acquires this lock, so the fix for this might be a matter of excluding that opCtx at that particular point from Flow Control.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              daniel.gottlieb Daniel Gottlieb
              Reporter:
              maria.vankeulen Maria van Keulen
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              16 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: