Implement mechanism for routers to bypass collection UUID consistency in ShardRole API for resharding relaxed=true mode

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-03-17
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-90448 introduced a relaxed=true mode for resharding, which is meant to be used to remediate situations where the sharding and shard-local catalogs have gone out of sync respect to the what a collection's UUID is.

      However, now that SERVER-78724 is switching aggregations to use the ShardRole API, which has stricter checks than the AutoGet, resharding(relaxed=true) is failing due to one of these checks – precisely because of the UUID mismatch it is looking to address.

              Assignee:
              Jordi Serra Torrens
              Reporter:
              Jordi Serra Torrens
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: