Projectrjs keeps overflowing its allowed MongoLab storage
gardym opened this issue · comments
We currently cache Tweets and 'Grams locally, as well as our own generic Event.
The Tweets collection grows rapidly and we are nearly out of free space on our MongoLab instance.
When we are out of free space, no more data is saved into any of the collections in the database, so we drop data on the floor.
You thinking another reactor job that trims the backlog based upon a set time window?
It's a nice idea(?) to store the raw data from our providers, but is it necessary?
We have two options:
- don't store the data
- store the data and increase our Mongo size
It might be best to toggle off the storing of the Tweets and 'Grams as they are not currently used by the application.
Thoughts?
I'd say turf the raw data and just keep our events. That would give us more of a runway on the current Mongo plan.
We can look at the auto trimming afterwards.