-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Run cleanup of old upload parts in background job #8759
Comments
Yes we should! |
The problem with this is that it is required to be on login to have a valid user session as it sets up the view. @icewind1991 Is there a way to set this up without the current session? Could you point me at some code that does this so I can come up with a first draft of the fix. Would love to have this fixed in 14 finally. |
I noticed a user with more than 20 GB used disk space and a quota of 5 GB. The folder username/uploads needs about 15-20 GB. The command After I have deleted most of his files (he knows about it ;) ), his personal files take about 40 MB. The upload folder is shrunk to 15 GB. Does this situation have anything to do with this ticket? How can I clean up the upload folder? |
The user should logout and login again. Then a cleanup is triggered. |
Most of this is addressed in #12227 |
Let's close it as it is now. |
Hello. Are there any news about this issue? I'm using S3 and, seems, unfinished uploads persist even after logout/login. |
Currently the cleanup of the upload folder is run as a login hook:
server/lib/base.php
Lines 808 to 834 in 20f1f75
We should do this as a background job.
@icewind1991 @rullzer @nickvergessen Opinions?
Should issues like #8753
The text was updated successfully, but these errors were encountered: