-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Internal Code, Replication
-
Labels:None
-
Fully Compatible
-
v5.0
-
Sharding 2021-07-12, Sharding 2021-07-26, Sharding 2021-08-09
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.
- is depended on by
-
SERVER-67077 TransactionCoordinator uses both the Grid fixed executor and the executor on the AsyncWorkScheduler
-
- Open
-
-
-
- Closed
-