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

Deadlock in the shard filtering metadata refresh path

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 7.0.0-rc1
    • Affects Version/s: 7.0.0-rc0, 6.0.5, 5.0.17, 4.4.21, 6.3.1
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v7.0
    • Sharding EMEA 2023-05-15
    • 107

      More context is available in the more general SERVER-76834.
      This ticket is specifically to avoid the known deadlocks on the shard filtering metadata refresh path:

      • ShardFilteringMetadataRefresh: Takes both PBWM and a ticket, but doesn't need to wait on the PBWM, neither on a ticket, because it doesn't do any storage engine work itself.
      • ShardServerCatalogCacheLoader: Takes both PBWM and a ticket. The PBWM is required for correctness, but it should skip the ticket acquisition.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: