improvement: add new ARGILLA_DATABASE_SQLITE_TIMEOUT
environment variable setting
#5213
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.
Description
On the distribution task testing effort meeting we found some errors raised by SQLite when the database was locked because too many writes were executed concurrently.
Increasing the timeout for SQLite reduces this problem, specifically changing the connection
timeout
parameter from the default value of5
seconds to30
seconds make the problem totally disappear locally.In this PR I have added a new
ARGILLA_DATABASE_SQLITE_TIMEOUT
environment variable that allow us to set a value for this. With a default value of15
seconds.The idea is to test this change on Spaces using a value of
30
seconds.Refs #5000
Type of change
How Has This Been Tested
Checklist