Use of S3 needs GridFS to work, how about the data saved in the database? Can we flush it?

Question

Use of S3 needs GridFS to work, how about the data saved in the database? Can we flush it?

pedrofg opened this issue 7 years ago · 1 comments

Hello Guys, I see the number of data increasing in the database using the CollectionFS S3 since it creates some temporary tables to save the images. How it handles those tables? Does it have a maximum limit? Should we flush those tables when we want?

Answer 1 · 2018-06-25T21:55:05.000Z

I have a cron job that flushes those tables every day, for some reason those tables make my deployments (using passenger) crash when they are above ~200 records.

Take into account that this will try to delete the documents from your S3 store, what I've done to overcome this problem is to not include delete rights for your AWS key, that way the library won't be able to delete those documents from S3 and only from the tables.