[SERVER-33032] add a DatabaseShardingState containing the databaseVersion as a decoration on Database Created: 31/Jan/18 Updated: 29/Oct/23 Resolved: 26/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.7.1 |
| Fix Version/s: | 3.7.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2018-02-12, Sharding 2018-02-26, Sharding 2018-03-12 |
| Participants: |
| Description |
|
Once However, the CatalogCache should not be used for version checking on shards (since the version check must be done under some form of database lock and the CatalogCache refresh does not take a database lock). Instead, we should create a DatabaseShardingState (analogous to CollectionShardingState), where we can load the databaseVersion for version checking on shards. We should make the new DatabaseShardingState a decoration on the storage catalog's Database (rather than on the ServiceContext, as the map of CollectionShardingStates is). |
| Comments |
| Comment by Githook User [ 26/Feb/18 ] |
|
Author: {'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi', 'username': 'EshaMaharishi'}Message: |