This call is copying the entire chunk map which can contain thousands or even millions of chunks. This can take a very long time, and so having this as part of the getShardIdsForRange function is very dangerous as it can introduce huge performance hits if used incorrectly.
This is also used in very few places for analyzeShardKey, so we should separate this logic out to make the router paths more resilient and less risky.
- is caused by
-
SERVER-68755 Make ChunkManagerTargeter return targeted chunk ranges in addition to targeted shard end points
-
- Closed
-
- is related to
-
SERVER-95452 Prevent CollectionRoutingInfoTargeter from iterating all chunk ranges during update and delete
-
- Closed
-
-
-
- Open
-
-
-
- Backlog
-
-
SERVER-97844 Improve handling of Chunk Ranges
-
- Backlog
-
- related to
-
-
- Backlog
-