[SERVER-21029] Don't abort dropDatabase because of too many collections Created: 20/Oct/15 Updated: 06/Dec/22 Resolved: 03/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.1.9 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | 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 | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
https://github.com/mongodb/mongo/blob/r3.1.9/src/mongo/s/config.cpp#L653
|
| Comments |
| Comment by Kaloian Manassiev [ 03/May/18 ] |
|
Gone away in 3.4 as part of the rewrite of the CatalogCache. |
| Comment by Kaloian Manassiev [ 01/Aug/17 ] |
|
Given that it can be worked around by calling dropDatabase repeatedly and because we haven't seen any reports for it, we do not need to do it for 3.6 and can wait for proper fix through the 'Collection Lifecycle' project. |
| Comment by Esha Maharishi (Inactive) [ 01/Aug/17 ] |
|
kaloian.manassiev, does this need to be done for 3.6? Or can it be moved back into Collection Lifecycle? |