Investigate the feasibility of keeping up to date or removing the connCache from FSM workloads

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • CAR Team 2025-08-04, CAR Team 2025-08-18, CAR Team 2025-09-01
    • None
    • 3
    • TBD
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      In add/remove shard suites (and also in config transition suites, though less problematically there due to the stability of the config server's shard id), the connCache's list of shards will become stale.

      This ticket is to investigate replacing the connCache (at least the shard list portion) with topology discovery helpers or keeping the connCache updated as the add/remove shard hook executes.

      We would like to know how much work this will be given that there are currently only 4 tests relying on the connCache that run in add/remove shard suites.

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

                Created:
                Updated: