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

FlowControlRefresher can be shut down while there are operations needing flow control tickets

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.14
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2019-06-03
    • 0

      The FlowControlRefresher periodic task is shut down as part of the node shut down procedure. If there are insufficient tickets available, certain operations will not receive a ticket and will hang.

      A potential fix for this issue could be to identify all operations that occur during shutdown and exclude them from flow control.
      Alternatively, the PeriodicRunner shutdown block can be moved to after the final global lock acquisition during shutdown.
      A third fix is to add synchronization handling upon shutdown of the FlowControlRefresher thread to circumvent ticket acquisitions. This third fix seems the most promising.

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

              Created:
              Updated:
              Resolved: