rally database gets locked

Bug #1804769 reported by Daniel Haupt
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Rally
Invalid
Undecided
Unassigned

Bug Description

Hi,

when I run several rally jobs at the same time (I have 10 jobs running every 5 minutes), I often get following error:

(sqlite3.OperationalError) database is locked [SQL: u'UPDATE tasks SET updated_at=?, status=? WHERE tasks.id = ?'] [parameters: ('2018-11-23 07:38:04.244077', 'validating', 2512)] (Background on this error at: http://sqlalche.me/e/e3q8)
Looks like Rally can't connect to its DB.
Make sure that connection string in rally.conf is proper:
sqlite:////opt/rally/db/rally.sqlite

Of course, the connection string in rally.conf is fine. A next run of the failed rally job will succeed.

I am using rally 1.2.1 (https://github.com/openstack/rally/releases/tag/1.2.1)

Daniel Haupt (danhaupt)
description: updated
Revision history for this message
Andriy Kurilin (andreykurilin) wrote :

Hi Daniel. It is a specific behavior of SQLite backend. Multiple processes can be doing a SELECT at the same time. But only one process can be making changes to the database at any moment in time, so SQLite applies specific locks.
If you would like to write the results from several processes, I suggest you to use Postgres or MySQL backends.

Changed in rally:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.