Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
4.4.2
-
Fully Compatible
-
ALL
-
v4.4
-
-
24
Description
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.
Attachments
Issue Links
- related to
-
SERVER-59924 Error executing aggregate with $out with "available" read concern on sharded clusters
-
- Closed
-