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

ReshardingCollectionCloner uses primary read preference when nearest was intended

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • v5.1, v5.0
    • Sharding 2021-11-29, Sharding 2021-12-13
    • 2

    Description

      sharded_agg_helpers::dispatchShardPipeline() uses the read preference set on the OperationContext already and therefore ignores the read preference on the AggregateCommandRequest that's passed into sharded_agg_helpers::targetShardsAndAddMergeCursors() by ReshardingCollectionCloner.

      Acceptance criteria: Run reshard_collection_cloner.js and manually verify the profiler entry for the aggregate command can be found on a secondary. If possible, also verify the $readPreference for the aggregate was sent with nearest

      Attachments

        Issue Links

          Activity

            People

              brett.nawrocki@mongodb.com Brett Nawrocki
              max.hirschhorn@mongodb.com Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: