[SERVER-27467] Remove double loading of the sharding database metadata entry Created: 19/Dec/16  Updated: 27/Feb/17  Resolved: 27/Feb/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.4.0, 3.5.1
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-20854 Don't refresh database and collection... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-01-02, Sharding 2017-02-13, Sharding 2017-03-06
Participants:

 Description   

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.



 Comments   
Comment by Kaloian Manassiev [ 27/Feb/17 ]

This will be achieved as part of the other ChunkManager reload changes.

Generated at Thu Feb 08 04:15:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.