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

Create a non-blocking API for the Fetcher class (or create an alternate class)

    XMLWordPrintable

Details

    • Fully Compatible
    • v5.0
    • Sharding 2021-07-12, Sharding 2021-07-26, Sharding 2021-08-09

    Description

      The Fetcher class only has a blocking way of waiting for outstanding requests to complete. This is a problem in cases where we need to use the Fetcher from inside a thread pool. We should either create an alternative Fetcher class (e.g. AsyncFetcher) that provides a non-blocking version of the same functionality, or refactor the AsyncFetcher to allow it to provide both blocking and non-blocking APIs, and probably implement the blocking ones in terms of the non-blocking ones.

      Attachments

        Issue Links

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-67077 TransactionCoordinator uses both the Grid fixed executor and the executor on the AsyncWorkScheduler

          • Major - P3 - Major loss of function.
          • Blocked

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-54208 Remove blocking call to Fetcher::join from TenantMigrationDonorService

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              jason.zhang@mongodb.com Jason Zhang
              matthew.saltz@mongodb.com Matthew Saltz
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: