[SERVER-54977] Clarify that admin database collections cannot be dropped in sharded topology only Created: 04/Mar/21 Updated: 29/Oct/23 Resolved: 26/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.7.0 |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Oleg Pudeyev (Inactive) | Assignee: | Antonio Fuschetto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding 2021-04-05 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
In 4.7.0, attempting to drop any collection in the admin database produces (due to https://jira.mongodb.org/browse/SERVER-35804) the following error: > Mongo::Error::OperationFailure: Cannot drop collection in admin database (20) (on localhost:27017) This error message claims that collections cannot be dropped in the admin database. However, collections in admin database can very well be dropped in standalone and replica set topologies; the prohibition is only applicable in sharded clusters. The current wording was quite confusing to me when I first encountered it. I suggest explicitly stating that the prohibition only extends to sharded clusters. Besides admin database, the config database appears to be similarly affected. |
| Comments |
| Comment by Githook User [ 26/Mar/21 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |
| Comment by Kaloian Manassiev [ 18/Mar/21 ] |
|
This ticket is just about improving the error message. In sharding it is not safe to drop any of the config collections and users shouldn't be using config for their use cases. |