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

Investigate whether the CatalogCache should bubble up a ShardCannotRefreshDueToLocksHeld when consulting Routing Information

    • Catalog and Routing
    • CAR Team 2024-11-25

      After SERVER-95393 [Dedicate a catalog cache and loader to the shard role] work, the shard now uses a ConfigServerCatalogCacheLoader to refresh its routing information.

      Currently, if a shard's routing information is stale during a transaction, attempting to refresh the CatalogCache entry for a shard may trigger a ShardCannotRefreshDueToLocksHeld error. This approach may be overly pessimistic, given that the shard—whether primary or secondary—can now refresh its routing information through the config server without needing to write anything to disk nor take any locks.

      The purpose of this ticket is to track an investigation into whether it is possible to refresh the CatalogCache within the transaction without generating a ShardCannotRefreshDueToLocksHeld error when consulting routing information.

            Assignee:
            Unassigned Unassigned
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: