We are facing a database size increase in our MongoDB 5 server since we've upgraded some gems including this one from our Rails 6.1 application.
Basically, when deleting a model that has a Carrierwave mounter with the :grid_fs storage engine, it destroys the GridFs::File but not the associated GridFs::Chunk.
I can't find any test from this gem checking for the cleaning of the chunks since, I guess, it's up to the mongoid-grid_fs gem to take care of it.
Have anyone experienced this issue ?
We are facing a database size increase in our MongoDB 5 server since we've upgraded some gems including this one from our Rails 6.1 application.
Basically, when deleting a model that has a Carrierwave mounter with the
:grid_fsstorage engine, it destroys theGridFs::Filebut not the associatedGridFs::Chunk.I can't find any test from this gem checking for the cleaning of the chunks since, I guess, it's up to the
mongoid-grid_fsgem to take care of it.Have anyone experienced this issue ?