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

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding EMEA
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Sharding EMEA
              Reporter:
              Marcos José Grillo Ramirez
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: