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

fix[next]: Guard diskcache creation by file lock #1745

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

tehrengruber
Copy link
Contributor

No description provided.

i.e. it ensures that any resources associated with the cache are properly
released when the instance is garbage collected.
This class extends `diskcache.Cache` to ensure the cache is properly
- opened on a distributed file system by using a file lock. This guards the creating of the
Copy link
Contributor

Choose a reason for hiding this comment

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

Is writing not a problem? Except that it's much harder to make all processes write at the same time and there less likely to trigger.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, writing to the cache is actually fine. SQLite which is used internally by diskcache.Cache handles concurrency very well in most cases, except for changing settings of the database itself, and that is the problem here. On creation of the diskcache.Cache object, some sql PRAGMA statements are executed and they lead to the observed issues. It is not really clear why, this should work, but it doesn't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants