-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Requesting memory issue #1584
Comments
This is a very strange bug in Cactus and/or Toil where To run on multiple nodes: |
Thanks a lot Glenn!! The |
Hi @glennhickey, I'm having more resource-related problems. Attached you can find the log of cactus.
What I can understand is that it seems to be and insufficient cores and disk space for the specified parameters: I resquested: and I'm running what flags should I use to adjust the run? |
Hi,
I'm getting errors regarding the memory I'm using/requesting with
cactus
.I submitted a job with the following options:
and I'm executing cactus wit these options:
--maxMemory 490G --binariesMode local --stats --logFile cactus.log --defaultCores 50 --defaultMemory 490G
... and I'm getting this error:
What am I doing wrong? what is the difference between '--maxMemory' and
--defaultMemory
? Will I get the same kind of error for--defaultCores
and--maxCores
?On a related problem. Would be possible to run
cactus
on multiple nodes? If so, how should I set these options?Thanks a lot
F
The text was updated successfully, but these errors were encountered: