[SERVER-72854] Feature flag fetching indexes in catalog cache Created: 13/Jan/23 Updated: 29/Oct/23 Resolved: 18/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2583-Milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding EMEA 2023-01-23 | ||||
| Participants: | |||||
| Linked BF Score: | 105 | ||||
| Description |
|
Currently, fetching indexes as part of getting routing information from the catalog cache is not feature flagged since the mongos does not have a concept of FCV. However, we are seeing a performance impact of fetching the global index information when a collection is accessed by a mongos for the first time. This ticket is to feature flag the fetch of index information based on the binary. It's not a perfect solution since once the feature flag is enabled, we will still have the performance hit without global indexes, but this will prevent there being a performance hit in upcoming releases while |
| Comments |
| Comment by Githook User [ 18/Jan/23 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |