Skip to content
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

Make chunk cache ttl configurable #24812

Merged
merged 3 commits into from
May 25, 2016

Conversation

PVince81
Copy link
Contributor

Continuation of #23486

Please review @icewind1991 @nickvergessen @schiesbn @rullzer

CC @guruz

fkammer and others added 2 commits May 24, 2016 14:55
This makes it less generic and only used for actual file chunking
@PVince81
Copy link
Contributor Author

Fixes #23455

@PVince81
Copy link
Contributor Author

Hmm, I should probably rename the value to "chunk_ttl" since the value now only applies to chunks

@icewind1991
Copy link
Contributor

Hmm, I should probably rename the value to "chunk_ttl" since the value now only applies to chunks

Yes that would be a lot better

👍 otherwise

@rullzer
Copy link
Contributor

rullzer commented May 24, 2016

@PVince81 wouldn't it make more sense to have some more logic for chunks?

So update the mtime of all chunks (if it is more than X difference?) so... that way as long as the user resumes upload withing a certain ttl no chunks will be removed. Also makes sense from kind of an abstract point that you never want to delete chunks of a file that you are actively uploading...

* issues uploading very large files via the ownCloud Client as upload isn't
* completed within one day.
*/
'cache_folder_gc_ttl' => 86400, // 60*60*24 = 1 day
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I should probably rename the value to "chunk_ttl" since the value now only applies to chunks

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, pushed

@PVince81
Copy link
Contributor Author

@rullzer yes, but that is more complex and can be done separately.

Here I was mostly taking over @fkammer's TTL addition.

@rullzer
Copy link
Contributor

rullzer commented May 24, 2016

Ok. fine by me then 👍

@guruz
Copy link
Contributor

guruz commented May 24, 2016

I think this value is too low, especially if there is nothing done like @rullzer had recommended
(e.g. taking the newest chunk as lifetime for all chunks).

Especially if a user shuts down his/her machine at night or is travelling or [...] ?

@PVince81
Copy link
Contributor Author

@guruz this was always the default. Won't change it in this PR. The purpose of this PR is making it configurable.

If you want a higher default value, please raise a separate ticket.

@guruz
Copy link
Contributor

guruz commented May 24, 2016

👍

@PVince81 PVince81 merged commit b5f455f into master May 25, 2016
@PVince81 PVince81 deleted the fkammer-enhancement-cache-folder-gc-ttl branch May 25, 2016 09:07
@lock
Copy link

lock bot commented Aug 5, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants