Skip to content

Conversation

@rhc54
Copy link
Contributor

@rhc54 rhc54 commented Apr 5, 2017

…ipate (i.e., didn't have any local children) in a job, clean up all resources associated with that job upon its completion. With the advent of backend distributed mapping, nodes that weren't part of the job would still allocate resources on other nodes - and then start from that point when mapping the next job. This change ensures that all daemons start from the same point each time.

Signed-off-by: Ralph Castain rhc@open-mpi.org

…ipate (i.e., didn't have any local children) in a job, clean up all resources associated with that job upon its completion. With the advent of backend distributed mapping, nodes that weren't part of the job would still allocate resources on other nodes - and then start from that point when mapping the next job. This change ensures that all daemons start from the same point each time.

Signed-off-by: Ralph Castain <rhc@open-mpi.org>
@rhc54
Copy link
Contributor Author

rhc54 commented Apr 5, 2017

@hjelmn This should fix the DVM behavior you observed during launch tests

@rhc54 rhc54 merged commit 9cb18b8 into open-mpi:master Apr 5, 2017
@rhc54 rhc54 deleted the topic/dvm branch April 5, 2017 01:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant