Re: [galaxy-dev] Huge Output Files in Galaxy (in compute cluster)

2011-04-29 Thread Dannon Baker
Yes, metadata can be set on a separate node. To do this you'll want to set the following value in your universe_wsgi.ini: set_metadata_externally = True -Dannon On Apr 29, 2011, at 9:16 AM, Marc Bras wrote: > Dannon, > > First of all, thank you for your reply ! > > In the datatypes_conf.xml

Re: [galaxy-dev] Huge Output Files in Galaxy (in compute cluster)

2011-04-29 Thread Marc Bras
Dannon, First of all, thank you for your reply ! In the datatypes_conf.xml, I attribute 'max_optional_metadata_filsize' but it's still very long... (althought I feel it getting better). However, when I run 'top' on the cluster computer's terminal, I see a python script running on the master

Re: [galaxy-dev] Huge Output Files in Galaxy (in compute cluster)

2011-04-22 Thread Dannon Baker
Marc, What you're seeing is likely Galaxy setting metadata like line counts, etc. One first step would be to check your datatypes_conf.xml and look for the attribute max_optional_metadata_filesize. You can set this on a per-filetype basis, or, if you'd like to set it for everything, you could

[galaxy-dev] Huge Output Files in Galaxy (in compute cluster)

2011-04-22 Thread Marc Bras
Hi All, I use Galaxy on a compute cluster and each job is launch in a node. When I launch a workflow and when it generates very huge files (some Go), the job finish (I can see that with 'qstat' command) but Galaxy takes several minutes (or some hours !!) to display a green Box in history. It s