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

SQLite can throw database locked error during write #28

Closed
adamgreig opened this issue Nov 26, 2014 · 1 comment
Closed

SQLite can throw database locked error during write #28

adamgreig opened this issue Nov 26, 2014 · 1 comment
Labels

Comments

@adamgreig
Copy link
Owner

If someone else is reading (or writing) the database when a result comes in over the network, it can't be written as the database is locked. Should really retry or at least catch exception rather than having it kill the server.

@adamgreig adamgreig added the bug label Nov 26, 2014
@adamgreig
Copy link
Owner Author

This is quite probably related to: http://beets.radbox.org/blog/sqlite-nightmare.html

Increasing the timeout should help. Implementing Python-level locks as in the link is difficult as the DB is accessed from multiple processes (e.g. one process loading data to chart while another is still running the server to accept new data).

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

No branches or pull requests

1 participant