[SERVER-75436] Only fetch index information from the index cache if the placement information is sharded Created: 29/Mar/23  Updated: 29/Oct/23  Resolved: 17/Apr/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Allison Easton Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-04-03, Sharding EMEA 2023-04-17
Participants:

 Description   

With the introduction of the index cache to the catalog cache, getting the routing information fetches the placement information from the collection cache and then the index information from the index cache. However, there can be no global indexes on an unsharded collection, so we can forgo fetching the index information from the cache if the placement information we found is unsharded.

This is important because it means that for unsharded collections, we will do one less trip to the config server for a newly accessed collection (we are pushing the first refresh of the index information for when the collection becomes sharded).



 Comments   
Comment by Githook User [ 17/Apr/23 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-75436 Only fetch index information from the index cache if the placement information is sharded
Branch: master
https://github.com/mongodb/mongo/commit/4806a899dd4ee131aa97e3f976d7ea72664debe4

Generated at Thu Feb 08 06:30:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.