Check for shard key index before using it to calculate split point with random migration fail point

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2026-03-02
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If the random migrations failpoint is enabled, we calculate a random split point to use for a moveRange command in order to test with more chunks. This random split point generation is using a shard key index, which may not exist for hashed shard keys. Similar to what we do in AutoSplitVector, we should first check if the shard key index exists before using it.

            Assignee:
            Allison Easton
            Reporter:
            Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: