-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
ALL
-
Sharding 2018-04-23
This is because mongos will only refresh an entry it has already cached if it is told the entry is stale.
However, it will only be told the entry is stale if it receives StaleDbVersion from some shard, which can only happen if it attaches a databaseVersion in the request to the shard (and of course, mongos won't attach a database version if its cache entry does not have a database version).
- is related to
-
SERVER-33783 Make shards and mongos do full routing/filtering metadata refresh after FCV change
- Closed