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

Make sure ExecutorPool gets terminated after migrations have completed

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.1, 7.3.0-rc0, 7.0.5
    • Affects Version/s: 4.2.0, 4.4.0, 5.0.0, 6.0.0, 7.0.0, 7.2.0
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v7.2, v7.0, v6.0, v5.0, v4.4
    • CAR Team 2023-12-25
    • 0

      When the system is being shutdown, it might happen that migrations are still ongoing [in cleanup], while the ExecutorPool they schedule work on gets terminated. In order to prevent this, we should make sure that all migrations have completed before the ExecutorPool they use terminates.

            Assignee:
            robert.sander@mongodb.com Robert Sander
            Reporter:
            robert.sander@mongodb.com Robert Sander
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: