Hi Roberto, Hans-Rudolf,

I can confirm from personal testing that enabling the
parallelism task-splitting in Galaxy does not work
well with SQLite.

This caused me problems with development and
testing since my development Galaxy instance uses
SQLite. As you found, testing with smaller splits
is one way round this, to reduce the chances of
a database lock.

We use PostgreSQL as recommended on our
production Galaxy instance with parallelism enabled,
and it works nicely.


On Thu, Feb 5, 2015 at 1:53 PM, Hans-Rudolf Hotz <h...@fmi.ch> wrote:
> Hi
> I can't promise, this is the solution for your specific problem, but you
> will always run into "database is locked" issue, when using SQLite.
> Hence, I strongly recommend to switch to a PostgreSQL database as the
> back-end for Galaxy (see also:
> https://wiki.galaxyproject.org/Admin/Config/Performance/ProductionServer#Switching_to_a_database_server
> )
> Hans-Rudolf
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:

To search Galaxy mailing lists use the unified search at:

Reply via email to