Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-55330

Rewrite ReshardingOplogFetcher to use Pipeline instead of Fetcher

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

      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:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: