Rewrite ReshardingOplogFetcher to use Pipeline instead of Fetcher

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Cluster Scalability
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Cluster Scalability
              Reporter:
              Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: