I re-read the docs and I was wrong on the default behavior. The default is "no" which just means don't oversubcribe the individual resources where I thought it was default to 'exclusive'. So I think I've been taking us down a dead end in terms of what I thought might help. :\
I have a system her that we are running with the elastic setup but there we are doing exclusive (and it's sent that way in the conf) scheduling so I've not run into the same circumstances you have. -- Brian D. Haymore University of Utah Center for High Performance Computing 155 South 1452 East RM 405 Salt Lake City, Ut 84112 Phone: 801-558-1150, Fax: 801-585-5366 http://bit.ly/1HO1N2C ________________________________________ From: slurm-users [slurm-users-boun...@lists.schedmd.com] on behalf of Chris Samuel [ch...@csamuel.org] Sent: Monday, September 10, 2018 4:17 PM To: slurm-users@lists.schedmd.com Subject: Re: [slurm-users] Elastic Compute On Tuesday, 11 September 2018 12:52:27 AM AEST Brian Haymore wrote: > I believe the default value of this would prevent jobs from sharing a node. But the jobs _do_ share a node when the resources become available, it's just that the cloud part of Slurm is bringing up the wrong number of nodes compared to what it will actually use. -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
