[SERVER-68755] Make ChunkManagerTargeter return targeted chunk ranges in addition to targeted shard end points Created: 11/Aug/22  Updated: 29/Oct/23  Resolved: 17/Oct/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Israel Hsu
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-68758 Make analyzeShardKey command calculat... Closed
Related
is related to SERVER-68754 Make ChunkManagerTargeter support tak... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2022-10-03, Sharding 2022-10-17
Participants:

 Description   

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 (SERVER-68754) and to figure out which chunk ranges each query targets. Currently, the ChunkManagerTargeter and ChunkManager only return the shard ids that each query targets. So we need to make the target methods also return chunk ranges. 



 Comments   
Comment by Githook User [ 17/Oct/22 ]

Author:

{'name': 'Israel Hsu', 'email': 'israel.hsu@mongodb.com', 'username': 'israelhsu'}

Message: SERVER-68755 Implement ChunkManagerTargeter outputting chunk ranges
Branch: master
https://github.com/mongodb/mongo/commit/c73958b4f0ba6180f920105d77af0a51ebd456e2

Generated at Thu Feb 08 06:11:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.