Latest
Open
RNA-Seq
ChIP-Seq
SNP
Assembly
Forum
Planet
All »
Home
Log In
Question: megablast to long
0
gravatar for gonzalo.greif
3.1 years ago by
gonzalo.greif • 0
Uruguay
gonzalo.greif • 0 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

 

thanks

Gonzalo
megablast time • 748 views
ADD COMMENT • link •
modified 3.1 years ago by Jennifer Hillman Jackson ♦ 25k • written 3.1 years ago by gonzalo.greif • 0
0
gravatar for Jennifer Hillman Jackson
3.1 years ago by
Jennifer Hillman Jackson ♦ 25k
United States
Jennifer Hillman Jackson ♦ 25k wrote:

Hello,

A http://usegalaxy.org, 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: https://trello.com/c/LNSxlzGq

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

Dataset_status_and_how_jobs_execute

All about Histories

Account, quotas, jobs, and clusters defined for http://usegalaxy.org

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

Best, Jen, Galaxy team
ADD COMMENT • link written 3.1 years ago by Jennifer Hillman Jackson ♦ 25k
Please log in to add an answer.

Similar posts • Search »

Content
Help
Access
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