bug: 'database is locked' error after some time without calling the API #71
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After a period of inactivity, the API returns an internal server error caused by a database error:
error saving the census on the database error="database is locked"
.After a few requests with this error, the API starts working without any issue.
At the moment we do not know how much time of inactivity is required to reproduce the error.
Original trace:
We found some references about SQLite
database is locked
error on the official documentation of the SQL driver that we use (mattn/go-sqlite3) and in its issues mattn/go-sqlite3#274 (comment).