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

Collection routing info targeter might invalidate catalog cache entry when it shouldn't

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Catalog and Routing
    • 1

    Description

      After SERVER-60144 an invalidation of the catalog cache entry for the original namespace was added in the routing info targeter in case there is a stale info thrown by a shard because a timeseries collection was created under the original namespace while the command was on route. The problem with this approach is that we could be covering other type of errors in the code if the stale namespace received is not a timeseries.

      We should take an approach similar to SERVER-84368 and invalidate the cache ONLY if the stale namespace received in the error is a timeseries namespace.

      Attachments

        Activity

          People

            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: