[SERVER-42053] proactively drop newly empty databases (sharding) Created: 02/Jul/19 Updated: 25/May/23 Resolved: 25/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Catalog, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | sharding-common-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
in |
| Comments |
| Comment by Eric Milkie [ 02/Jul/19 ] |
|
This work depends on the ability of the config server to know about all collections, including unsharded ones, so this ticket depends on that project's completion. |