Hello,

Postgres did it perfectly, but as I would like to enable this option in my production servers I changed two configs in galaxy.ini:

# This enables splitting of jobs into tasks, if specified by the particular tool config.

# This is a new feature and not recommended for production servers yet.

use_tasked_jobs = True

local_task_queue_workers = 4

So I have two questions,

1. Why is this not appropriate for productions server yet?

2. What is local_task_queue_workers doing? I think I misunderstand something because I put this parameter in the tool config file:

on ther other hand, I don't see any documentation about parallelism tag, is there any?

Would you so kind to answer me, please?

Regards

On 5 February 2015 at 15:14, Peter Cock <p.j.a.cock@googlemail.com> wrote:

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.

Peter

On Thu, Feb 5, 2015 at 1:53 PM, Hans-Rudolf Hotz <hrh@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

Roberto Alonso

Functional Genomics Unit
Bioinformatics and Genomics Department
Prince Felipe Research Center (CIPF)

C./Eduardo Primo Yúfera (Científic), nº 3
(junto Oceanografico)
46012 Valencia, Spain
Tel: +34 963289680 Ext. 1021
Fax: +34 963289574
E-Mail: ralonso@cipf.es