-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse doesn't clear fs.chunks after a upload #3161
Comments
Not sure about that, but the memory error you mention is real :) |
The collection fs.chunks is where the files binary saved.And the fs.files collection save same file info.The collection who stores files just store the file names. |
Thanks @yangkghjh , you're right. I close this issue |
@yangkghjh @hydex86 that doesn't explain the memory retention issue, is it in the express middleware then? |
@flovilmart which memory retention issue are you talking about? Not sure if you found anything ese thanks to this :) |
The collection is in the database right? so that's not the process memory but the database? |
As @yangkghjh I was wrong. Data stored in fs.chunks are real files. The collection where I store the PFFiles would be pointers to those fs.chunks. |
Hi, I'm using parse-server in Heroku + mlab.
My client app uploads files to the server. Yesterday my client app was receiving an error 130 when saving a file to the server. I started to investigate and I found there was a collection called fs.chunks with 1 Gb of data, but the collection who stores files only had 50 Mb.
I think fs.chunks uploaded should be deleted after the save process completes successfully, isn't it? Which is the best way to manage this?
The text was updated successfully, but these errors were encountered: