Handle shardNotFound errors in bucket_unpacking_with_sort_extended_range

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2025-05-26
    • 0
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • 0

      This test calls enableSharding with a specific primary shard excluding the config shard in order to prevent problems with config transitions. Now that we are running arbitrary add/remove shards in the background, excluding the config shard is insufficient. Instead, we should add retry logic to choose a new shard in case of ShardNotFound errors.

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

                Created:
                Updated:
                Resolved: