Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Autoscale doesn't work properly with -N, only -n #5

Closed
anhoward opened this issue Nov 20, 2018 · 2 comments
Closed

Autoscale doesn't work properly with -N, only -n #5

anhoward opened this issue Nov 20, 2018 · 2 comments

Comments

@anhoward
Copy link
Contributor

When specifying -N <num_nodes> on a job, CycleCloud doesn't spin up the correct number of nodes and the job never runs. This is needed for MPI jobs wanting to use partial nodes.
@basnijholt basnijholt mentioned this issue Apr 26, 2019
Open
@aplamada
Copy link

aplamada commented May 7, 2019 •
edited
Loading

I experienced the same problem. In my simple salloc or srun examples -N is parsed as -n - in the cyclecloud GUI I noticed that the number of cores provisioned corresponds to -N . As a workaround I used the GUI to allocate the desired number of execute nodes.

@anhoward
Copy link
Contributor Author

anhoward commented Aug 2, 2019

This is fixed in the 7.8 CycleCloud release. Release notes are here.

@anhoward anhoward closed this as completed Aug 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aplamada @anhoward