Hi all, We are using PostreSQL for our production Galaxy server, but for development I am using SQLite. Typically it is just me is using the development server, so database contention has not generally been a problem.
However, while testing job splitting for breaking up tasks for the cluster, I have noticed today multiple problems with the database when queuing or running the sub-jobs: OperationalError: (OperationalError) database is locked My hunch is that all the child-jobs are created and added to the queue and some of this is happening in parallel leading to contention over the SQLite database. Does this sound likely? Is this something that could be more robust in Galaxy, or should I simply switch to a real database (SQLite or PostreSQL) for these tests? Thanks, Peter ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/