Question: megablast to long
gravatar for gonzalo.greif
3.1 years ago by
gonzalo.greif0 wrote:

Hi, I am running a megablast and is take too long, I launched in august 10 and is still runnning.

the API id is: bbd44e69cb8906b54b21e9e9f12b1cbf




megablast time • 748 views
ADD COMMENTlink modified 3.1 years ago by Jennifer Hillman Jackson25k • written 3.1 years ago by gonzalo.greif0
gravatar for Jennifer Hillman Jackson
3.1 years ago by
United States
Jennifer Hillman Jackson25k wrote:


A, a job can take up to 48 hours to executes (this runtime quota is good for large jobs!). In addition to that, if the job was initially launched on a smaller cluster, then failed for resource, it can then be submitted to a cluster with more compute. This queues it again and then it executes.

I would give this one more time to finish, otherwise the new job just starts back at the beginning again. Because it is long-running, there is still chance the job could fail for resource. And given that there is a known issue with Megablast right now, it may file for this reason:

To help with understanding what is going on and what to do if the job does fail. 


All about Histories

Account, quotas, jobs, and clusters defined for

Jobs that fail (Section 2.8) plus many other help topics: Galaxy Project Support hub

Best, Jen, Galaxy team

ADD COMMENTlink written 3.1 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: 175 users visited in the last hour