Loading...

XML

Word

Printable

JSON

Details

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.0.4, 5.1.0-rc0
Affects Version/s: None
Component/s: Internal Code, Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Requested:

v5.0
Sprint:
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

SERVER-67077 TransactionCoordinator uses both the Grid fixed executor and the executor on the AsyncWorkScheduler

Open

SERVER-54208 Remove blocking call to Fetcher::join from TenantMigrationDonorService

Closed

Activity

People

Assignee:: Jason Zhang

Reporter:: Matthew Saltz (Inactive)

Participants:: Githook User, Jason Zhang, Matthew Saltz, Vivian Ge

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Dates

Created:: Feb 02 2021 03:36:00 PM UTC

Updated:: Oct 29 2023 09:58:07 PM UTC

Resolved:: Aug 05 2021 07:00:45 PM UTC