I'm having a problem with "job waiting to run" and the job never running.
I have my own cluster so load is not an issue, in fact there does not seem to be much of a CPU load in the cloudman manager.
This has happened with a number of different tools, is this another way for the tool to fail?
Hello,
Are you using additional nodes or just the single primary node that the Galaxy server is also running on?
It sounds like you need to add more nodes. Perhaps add one or two, then see how that impacts job processing? There is also an option to "auto-scale" nodes - yet beware that this can run up costs unexpectedly. How much to invest in these options depends on how quickly you need to get your work done and how many people are using the cloud instance.
When most do workshops (where speed is important), we create several Cloudman instances (clones of each other) and try to have about 10 people working on each, and then allocate one node per person.
Hope this helps! If adding nodes does not help directly, perhaps try re-running the jobs first. Then based on how that works, please let us know if you need more assistance.
Jen, Galaxy team
I did have autoscale to 5 nodes selected, it opened a worker node, but there was no or little load on both nodes. The job just stays there, I have tried rerunning but the result is the same and also rebooting the the cluster, there are no other jobs running.
It has worked once before this problem.
manually adding 5 c3.large worker nodes fixes this, the job runs. Its a bit annoying that the cluster does not autoscale! Additionally there does not seem to be a way as admin to check job load/problems.
