-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Sharding 2022-09-19, Sharding 2022-10-03, Sharding 2022-10-17
To allow the analyzeShardKey command to determine if a candidate shard key can lead to a hot chunk, we need the ability to simulate routing based on the synthetic routing table created based on the candidate shard key. So we need to make the ChunkManagerTargeter support using synthetic routing info rather than the one from the CatalogCache to do the targeting.
- is depended on by
-
SERVER-68758 Make analyzeShardKey command calculate metrics about the hotness of shard key ranges
- Closed
- related to
-
SERVER-68755 Make ChunkManagerTargeter return targeted chunk ranges in addition to targeted shard end points
- Closed