Operational Defect Database
BugZero found this defect 68 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2606285
Remove check in dropCollectionCoordinator that prevents to drop a timeseries from its bucket namespace
Last update date:
3/14/2024
Affected products:
MongoDB Server
Affected releases:
8.0.0-rc0
Fixed releases:
No fixed releases provided.
Description:
Info
A check in shardsvr_drop_collection_command prevents a user from dropping a timeseries using the "bucket" namespace for a tracked collection. After SERVER-83878 the constraint has been relaxed and in case the registered collection is "unsplittable" the drop is possible. That was done to ensure feature parity with 7.0 where dropping a timeseries from it's bucket nss was possible for an unsharded collection. However, as part of SERVER-83878 it has been noticed it is possible to remove completely that check even for sharded collection as the collection will be removed successfully. In general, that check is not safe as performed outside the ddl lock. Any shardCollection might occur after the check, causing the drop to remove the sharded collection.
Top User Comments
Steps to Reproduce
