[SERVER-55330] Rewrite ReshardingOplogFetcher to use Pipeline instead of Fetcher Created: 19/Mar/21 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | PM-234 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
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 |