Doing so would (1) make ReshardingOplogFetcher more consistent with ReshardingCollectionCloner + ReshardingTxnCloner and (2) avoid eating a thread to block on the result of Shard::runAggregation(). Note that (2) implies removing RecipientStateMachine::_oplogFetcherExecutor and having ReshardingOplogFetcher receive the RecipientStateMachine's scoped task executor instead.
ReshardingOplogFetcher can also leverage the functions added to resharding_data_copy_util as part of SERVER-55329.
- depends on
-
SERVER-55329 Move methods on ReshardingCollectionCloner into resharding_data_copy_util
-
- Closed
-
-
SERVER-55566 Expand invariant checks in ARM to accommodate resharding pipelines
-
- Open
-