[SERVER-19291] Sharded dropDatabase should take distributed lock on database being dropped Created: 06/Jul/15 Updated: 13/Dec/22 Resolved: 13/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Done | Votes: | 0 |
| Labels: | AdiZ | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Sprint: | Sharding 8 08/28/15, Sharding 9 (09/18/15) | ||||||||
| Participants: | |||||||||
| Description |
|
Currently createDatabase takes the distributed lock, and enableSharding will soon, we should probably be taking it for dropDatabase as well. |
| Comments |
| Comment by Tommaso Tocci [ 13/Dec/22 ] |
|
Fixed as part of PM-1965 |