Info

After upgrading the mongo server from 3.2.6 to 3.4.24 on CentOS Linux 7.6, it seems that dropping collections gets slower in time. The application that uses mongo deletes ~10000 collections on startup (all of them are empty collections in our example). With mongo 3.4.24 this is fast (a few seconds) only the first time after the server is started. Afterwards each collection drop time increases (in one example it took 1h30 minutes to delete all collections after the server was running for just a few days). With the exception of the server upgrade, there was no other change in the application, mongo server configuration or the linux box. The issue can be replicated from mongo shell too with a script like: db.getCollectionNames().filter(function(name){ return name.match(regExp) }).forEach(function(collectionName){ db.getCollection(aCollectionName).drop() });

Top User Comments

carl.champain commented on Thu, 28 May 2020 14:40:30 +0000: Hi bogumil_h@yahoo.com, MongoDB 3.4 is already end-of-lifed, which means it is unsupported by us. We strongly recommend you upgrade to a supported version. If you need assistance troubleshooting, I encourage you to ask our community by posting on the MongoDB Community Forums or on Stack Overflow with the mongodb tag. Kind regards, Carl

Steps to Reproduce