-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Labels:None
-
Sharding EMEA
-
ALL
Stop forcing a routing info refresh at the very beginning of cluster moveChunk command we should rely on the shard versioning protocol that will ensure that eventually the mongos will retry the command according to the updated routing info