[SERVER-66863] Add a new Global Index Cache in the Router Role Created: 30/May/22 Updated: 29/Oct/23 Resolved: 04/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | 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 2022-08-22, Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
The collection sharding state API must be extended to also obtain the index metadata information. In order to do this, we need to implement an IndexCache, based on the ReadThroughCache (like the DatabaseCache or the CollectionCache), that will use the IndexVersion component as a base time to advance it. |
| Comments |
| Comment by Githook User [ 04/Oct/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |
| Comment by Marcos José Grillo Ramirez [ 10/Jun/22 ] |
|
kaloian.manassiev@mongodb.com I talked to max.hirschhorn@mongodb.com and they will need the router role changes. |
| Comment by Kaloian Manassiev [ 09/Jun/22 ] |
|
marcos.grillo@mongodb.com, I thought that at the first phase of the project (the one that is required by Global Index Maintenance) we will not have an index cache and instead we will use a transaction to update the Shard and the CSRS catalogs. Why do we need one now? EDIT: I just saw milestone 2 in the labels, but can you please confirm? |