Investigate if there's a lock ordering conflict in IndexBuildsCoordinatorMongod

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Execution Team 2025-02-17, Storage Execution 2025-03-03, Storage Execution 2025-03-17, Storage Execution 2025-03-31, Storage Execution 2025-04-14, Storage Execution 2025-04-28, Storage Execution 2025-05-12, Storage Execution 2025-05-26
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      As part of SERVER-99150 we've implemented a lock ordering checker across the database. It detected a lock ordering conflict with the commit quorum lock used in the class and the RSTL lock.

      The class has the following two lock orderings:

      As the commit quorum lock is exclusively locked and the RSTL lock is used during stepdown there might be a lock ordering conflict at play here that we haven't yet triggered. We should investigate if there's an actual issue and attempt to fix it if needed.

            Assignee:
            Malik Endsley
            Reporter:
            Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: