Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-68755

Make ChunkManagerTargeter return targeted chunk ranges in addition to targeted shard end points

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Sharding 2022-10-03, Sharding 2022-10-17

    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. 

      Attachments

        Activity

          People

            israel.hsu@mongodb.com Israel Hsu
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: