[SERVER-73184] Ensure collection locks are taken in proper order in the sharding index catalog API Created: 23/Jan/23 Updated: 26/Jan/23 Resolved: 26/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | PM-2583-Milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Participants: | |||||||||
| 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. |
| Comments |
| Comment by Marcos José Grillo Ramirez [ 26/Jan/23 ] |
|
This is going to be handled as part of SERVER-73212. |