Remove usages of non causally consistent ShardRegistry::getShardForHostNoReload accessor

XMLWordPrintableJSON

    • Catalog and Routing
    • 200
    • 3
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      This is the last standing non causally consistent accessor left in the ShardRegistry.

      Is currently used by ShardingTaskExecutor and in ShardingNetworkConnectionHook during response processing.

            Assignee:
            Unassigned
            Reporter:
            Tommaso Tocci
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: