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

Ensure collection locks are taken in proper order in the sharding index catalog API

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • Sharding EMEA

    Description

      For the sharding index catalog API we take two config collection locks on several operations, however, we're not ensuring the locks are being taking in resource id order. We should ensure we use the lock API properly to ensure the lock acquisition order like in this test file.

      Attachments

        Activity

          People

            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: