-
Notifications
You must be signed in to change notification settings - Fork 310
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
SGE slots_per_host doesn't work #471
Comments
What do you mean it doesn't work? I use this setting and it works as I expect |
I must be using some combination of settings that's invalidating it, then. With the config file below, the number of slots on each node remains at the default and they each suck up multiple jobs at once. Running
|
I have very similar settings and I do see that the number of slots is set to 1 on each of my hosts. StarCluster/starcluster/plugins/sge.py Line 100 in 286dc61
also, I don't think you can change the config after the cluster has been started. |
Somehow this is working for me now. With apologies, I'm going to close this issue as irreproducible. |
What is the git plugin? If it is what I think it is, take a look at #468 |
It's a little plugin I threw together to forward my git credentials to a cluster (ssh agent forwarding, set remote username/email) and pull some repos on cluster startup. The code is in my StarCluster fork. https://github.com/kevinbache/StarCluster/blob/develop/starcluster/plugins/git.py |
Setting
slots_per_host=1
doesn't seem to work. sshing in the master node and runningqconf -mattr exechost complex_values slots=1 <hostname>
does, however. Would you be interested in a pull request that changed the sge plugin to use this mechanism?The text was updated successfully, but these errors were encountered: