[SERVER-20135] dropDatabase should occur in parallel across shards Created: 26/Aug/15 Updated: 06/Dec/22 Resolved: 14/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Sharding |
| Affects Version/s: | 3.0.6 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andre de Frere | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding
|
||||
| Participants: | |||||
| Description |
|
In a sharded cluster, dropDatabase (and the component collection drops) appears to occur in serial. When databases, or the number of collections they contain are sufficiently large, the dropDatabase may not return quickly. This means that the time spent waiting will be exacerbated by the number of shards. |
| Comments |
| Comment by Kaloian Manassiev [ 14/Jun/18 ] |
|
Gone away starting in 4.0 as a result of dropDatabase using the ARS. |