No nodes in downed or drained state. These are nodes that are dynamically brought up and down via the powersave plugin. When the are taken offline due to being idle I believe the state is set to FUTURE by the powersave plugin.
-Sajesh- From: slurm-users <slurm-users-boun...@lists.schedmd.com> On Behalf Of Brian Andrus Sent: Wednesday, March 24, 2021 11:02 PM To: slurm-users@lists.schedmd.com Subject: Re: [slurm-users] Limit on number of nodes user able to request EXTERNAL SENDER Do 'sinfo -R' and see if you have any down or drained nodes. Brian Andrus On 3/24/2021 6:31 PM, Sajesh Singh wrote: Slurm 20.02 CentOS 8 I just recently noticed a strange behavior when using the powersave plugin for bursting to AWS. I have a queue configured with 60 nodes, but if I submit a job to use all of the nodes I get the error: (Nodes required for job are DOWN, DRAINED or reserved for jobs in higher priority partitions If I lower the job to request 50 nodes it gets submitted and runs with no problems. I do not have and associations or QOS limits in place that would limit the user. Any ideas as to what could be causing this limit of 50 nodes to be imposed? -Sajesh-
