-
Type: Improvement
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.0, 3.5.1
-
Component/s: Sharding
-
None
-
Fully Compatible
-
Sharding 2017-01-02, Sharding 2017-02-13, Sharding 2017-03-06
The sharding cache currently loads the database metadata entry twice - once as part of the cache check and once when the entire DBConfig is loaded. This is not necessary and also prevents some of the fields from being marked as const, specifically _primaryId.
Since we have no means of forcing the refresh of a database primary, there is no point in reloading this value each time we force reload of the collections in DBConfig::reload.
- is depended on by
-
SERVER-20854 Don't refresh database and collection information from config server while holding a mutex
- Closed