Investigate potential lock ordering conflict in ShardingCatalogManager

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-03-03
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In SERVER-99150 we've implemented a lock ordering checker. This checker has detected a conflict in the ShardingCatalogManager class.

      Inside of this class we have two lock orderings:

      We should investigate if there's a way to only have one ordering or if the current state is safe considering the FCV lock is taken in shared mode.

              Assignee:
              Allison Easton
              Reporter:
              Jordi Olivares Provencio
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: