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

Switch ReshardingCollectionCloner to run on a separate TaskExecutor

    • Fully Compatible
    • Sharding 2020-11-16

      The changes from ff6685c as part of SERVER-49787 had the ReshardingCollectionCloner run on the current thread for convenience with the testReshardCloneCollection command. Switching the ReshardingCollectionCloner to run on a separate TaskExecutor is a prerequisite to integrating the ReshardingCollectionCloner into the RecipientStateMachine. The RecipientStateMachine's thread needs to react to the mongo::Futures returned from multiple components (including ReshardingCollectionCloner) that are running concurrently.

            Assignee:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: