This is *almost* what I want, but not quite. When I do this, users can throw the "--exclusive=YES" flag and get an exclusive node. I guess I'd interpreted "Shared=FORCE" to mean that they could not do this, which is what I wanted. I'm not sure I understand, based on the documentation, why "Shared=FORCE" implies that cores and consumed differently.
Is there no way to disable "exclusive" while also getting what I want? Thanks, Paul. > On Apr 8, 2016, at 13:40, John DeSantis <[email protected]> wrote: > > > Paul, > > Try changing the Partition "Shared=FORCE" statement to "Shared=NO". > > We do that on all of our partitions and get the desired behavior. > > John DeSantis > > On 04/08/2016 01:06 PM, Wiegand, Paul wrote: >> >> Greetings, >> >> I would like to have our cluster configured (and believed I had done) to >> work as follows: >> >> * User jobs can share a node, but not cores and memory >> * Users cannot override the share option using "--exclusive" >> * Once assigned cores and memory, jobs are restricted to just those assigned >> resources >> >> >> But this is not what is happening. Instead, if jobs request a sufficiently >> small amount of memory that they can both consume their requested amounts >> without contention, slurm can and does deploy jobs to the same node ... even >> if there are an insufficient number of cores. Instead, the jobs alternate >> between a "suspended" mode and "running" mode and, of course, run much, much >> slower as a result. >> >> Clearly I've misunderstood my configuration. We are running Slurm 15.08.3. >> Here are what I believe are the relevant parameters from our slurm.conf. >> Let me know if you want me to provide more. >> >> >> ProctrackType=proctrack/cgroup >> TaskPlugin=task/cgroup >> >> SelectType=select/cons_res >> SelectTypeParameters=CR_Core_Memory >> >> PartitionName=DEFAULT Shared=FORCE State=UP DefaultTime=00:10:00 >>
