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

Ensure that BalancesCommandsScheduler synchs on every outstanding command before completing its stop() routine

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Backlog
    • None
    • Fully Compatible
    • Sharding EMEA 2022-02-07, Sharding EMEA 2022-02-21, Sharding EMEA 2022-03-07

    Description

      The stop() routine of BalancerCommandsScheduler is currently relying on a "fire&forget" strategy to cancel every outstanding request.

      While this minimises the execution time of the method, it exposes the class to potential data races in case remote responses to cancelled requests were still received after destroying the Scheduler.

      A more robust alternative consists on synching on the reception of every response during the stop() of the scheduler.

      Attachments

        Activity

          People

            paolo.polato@mongodb.com Paolo Polato
            paolo.polato@mongodb.com Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: