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

Refreshing the Routing Information only when we hit a targeting error

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Sharding EMEA
    • Sharding EMEA 2022-03-07, Sharding EMEA 2022-03-21, Sharding EMEA 2022-04-04

      the goal of this ticket is to recover some of the ideas introduced in PM-1633. 

      The default behavior of the CatalogCache is that if someone advanced the TimeInStore, the next call to getRoutingInfo* will fetch those changes from the CSRS. The idea of this ticket will be to only fetch those if after targetting with the cached routing information we get an StaleConfigInfo exception.

            Assignee:
            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: