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

Map reduce is versioned on direct connection to shards

    • Fully Compatible
    • ALL
    • v4.4
    • Hide

      1. Set up a replica set
      2. Add some data
      3. Restart the replica set with --shardsvr
      4. Add the replica set to a sharded cluster
      5. Run a mapreduce with output on the primary directly

      Show
      1. Set up a replica set 2. Add some data 3. Restart the replica set with --shardsvr 4. Add the replica set to a sharded cluster 5. Run a mapreduce with output on the primary directly
    • 24

      After SERVER-48128 the requests sent directly to a shard should not be versioned, so, there shouldn't be any cache refresh on the node that a direct client can't retry, however, this is not the case, there is a cache refresh that's being called when executing a mapReduceWrite. Running a jstest will show that during the direct client check, there is a refresh while doing a mapReduceWithWrite.

            Assignee:
            eric.cox@mongodb.com Eric Cox (Inactive)
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: