Operational Defect Database
BugZero found this defect 122 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2549827
Make cloneCollectionAsCapped work properly in case of concurrent DDLs
Last update date:
3/11/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
Disclaimer: the command is not currently exposed on the router and can only be directly called on shards. Once SERVER-80416 will expose cloneCollectionAsCapped, the problem will surface. The cloneCollectionAsCapped command is currently unsafe because is does not properly serialize with concurrent DDLs on the same namespace and will be even more unsafe "tomorrow" (once unsharded collections will be tracked) because it only performs changes on the local catalog. Purpose of this ticket is to fix such limitation. The new implementation could perform an aggregation to copy the documents and create the new capped collection. More details in this comment.
Top User Comments
Steps to Reproduce
