Question: Cuffdiff has been running for over 24 hours, without completing.
gravatar for b.conway-campbell
3.7 years ago by
United Kingdom
b.conway-campbell20 wrote:

I have run my standard CuffDiff workflow which usually finishes overnight. But this time the job is still running for over 24 hours and hasn't finished yet. Should I delete and start again, or just keep waiting? 


status main jobs galaxy resources • 1.3k views
ADD COMMENTlink modified 3.7 years ago by Jennifer Hillman Jackson25k • written 3.7 years ago by b.conway-campbell20
gravatar for Jennifer Hillman Jackson
3.7 years ago by
United States
Jennifer Hillman Jackson25k wrote:


If you are using the public Main Galaxy instance at, then this is how jobs are handled:

Section 2.6 = Dataset status and how jobs execute
Section 2.8.1-4 = 4. Job failure reason "ran longer than the maximum allowed job run time"

Then quotas are described in more detail here, see the table for "Compute resources". Currently all jobs on Main are using the default cluster. This cluster has a quota of 36 hours of wall-time (execution time).

In short, if the job is grey, that would be unexpected at this time unless you have several queued. Jobs will execute in the order submitted - wait for the other jobs to complete and then this job will queue when it is your turn to run a job again (jobs slots are allocated to users evenly). If the job is yellow, the job still has more time to complete running before hitting the "wall-time" for execution. If the job  is red because it eventually fails due to exceeding wall-time (or memory), you might be able to adjust parameters or will need to move to a local or cloud Galaxy where you can dedicate more resources.

Hopefully this helps, Jen, Galaxy team

ADD COMMENTlink written 3.7 years ago by Jennifer Hillman Jackson25k
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 167 users visited in the last hour