Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-72884

Remove usages of non causally consistent ShardRegistry::getShardForHostNoReload accessor

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Minor - P4 Minor - P4
    • None
    • None
    • None
    • Catalog and Routing
    • 3

    Description

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

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

      Attachments

        Activity

          People

            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: