-
Type: Task
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding EMEA
-
Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06
The normal refresh scenario should not be affected by changes for PM-1965, a regular incremental refresh due to stale data placement data should not incur in extra latency due to the presence of indexes in the sharded index catalog. The outcome of this ticket should be a measurement of the behavior of refreshes before and after the catalog cache changes, in order to ensure we're not penalizing regular collections operation due to the new refresh scheme.
- depends on
-
SERVER-72323 Improve the first refresh of a stale router by not getting the indexes by default
- Closed