search

ComparativeGenomicsToolkit / cactus

Official home of genome aligner based upon notion of Cactus graphs
Other
523 stars 111 forks source link

Running cactus on AWS: vCPU limit error #1159

Open tinaveit opened 1 year ago

tinaveit commented 1 year ago

Hi! We are running genome alignments of 8 species (11 GB total) using cactus on Amazon Web Services. We increased the On-Demand Standard (A, C, D, H, I, M, R, T, Z) instances to 300, but we are still getting this error:

"You have requested more vCPU capacity than your current vCPU limit of 300 allows for the instance bucket that the specified instance type belongs to".

However, we noticed the workflow progress is not affected by this error, and cactus continues to run. Our question is: based on your experience, do you recommend us increasing the vCPU limits even more or just try finishing the run with what we have?

This is the command that I am using to run cactus: cactus --consCores 2 --nodeTypes c4.8xlarge,r4.8xlarge --minNodes 0,0 --maxNodes 20,1 --nodeStorage 250 --provisioner aws --batchSystem mesos --metrics aws:us-east-1:cactus-xtremodevo-bucket --logFile cactus.log --rotatingLogging seqFile.txt output.hal

Thank you for your time and support!

glennhickey commented 1 year ago

I don't think I've ever seen that message before. If it's not crashing, I wouldn't worry too much. Will ping @adamnovak in case he has any ideas on the Toil side what's behind this...