BWA mapping taking >48 hours
Hello, I am not sure whether this is a bug or a problem with the server, or if it is just normal but I started a BWA mapping on some paired-end reads of a bacterium genome two days ago late evening. The job appears in yellow as 'running' but is it normal that is taking all these hours? I must say this is not the first time it happens. any advice? thanks stefano
Stefano, Certain jobs have up to 72 hours of run time on the public Main Galaxy server at https://main.g2.bx.psu.edu (usegalaxy.org). Other sites or your own site may have other limits. Jobs last different time lengths in general depending on processing needs and the capabilities of the server/cluster nodes they are running on. RNA-seq analysis tools can be quite compute intensive. If processing runs over 72 hours, the job will fail and either the run parameters/inputs will need to be modified to shorten the execution time or a local/cloud instance with sufficient resources (or another public instance) be used. Hope this helps to explain, Jen Galaxy team On 2/22/13 11:00 AM, stefano cardinale wrote:
Hello, I am not sure whether this is a bug or a problem with the server, or if it is just normal but I started a BWA mapping on some paired-end reads of a bacterium genome two days ago late evening. The job appears in yellow as 'running' but is it normal that is taking all these hours? I must say this is not the first time it happens. any advice? thanks stefano ___________________________________________________________ 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:
-- Jennifer Hillman-Jackson Galaxy Support and Training http://galaxyproject.org
participants (2)
-
Jennifer Jackson
-
stefano cardinale