[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:
Problem/Incident
is caused by SERVER-35804 Disallow dropping collections under c... Closed
Related
related to RUBY-2540 Add server 4.7 configurations to Ever... Closed
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: SERVER-54977 Clarify that admin database collections cannot be dropped in sharded topology only
Branch: master
https://github.com/mongodb/mongo/commit/144edad978b0f81c7d9f89f5e12697a246ff0dfc

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.

Generated at Thu Feb 08 05:35:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.