As I mentioned in my email, I used scontrol show node(s) in order to display the current order - I was more interested in understanding how the order is actually defined/set up by SLURM , as it is not defined in slurm.conf for dynamic nodes.
We assumed that it might be related to the time the node registers, but as I unregistered and re-registered and the node stayed in the same "order" I was wondering if there is some internal caching...

Also -Yes, you are right, we have the same Weights for all nodes - but we would like to avoid setting weights for our setup, only if not possible otherwise...- but thanks again for the hint!

So I would still like to clarify:

How SLURM determines the internal node order when nodes register dynamically given all weights/configs are the same ? (kinda : who/what defines the output of scrontrol show nodes)
Whether this order persists across node or controller restarts (i.e., if SLURM caches previous node information)?

Best, Greta

Dr. Greta Assmann

Data Analysis and Research Infrastructure

OBBA 230

Forschungsstrasse 111
5232 Villigen-PSI

email: greta.assmann@psi.ch

From: Ole Holm Nielsen via slurm-users <slurm-users@lists.schedmd.com>
Sent: 22 October 2025 15:02
To: slurm-users@lists.schedmd.com <slurm-users@lists.schedmd.com>
Subject: [slurm-users] Re: dynamic node slurm node list order

On 10/22/25 14:41, Patrick Pun via slurm-users wrote:
> You can get a node list by
> scontrol show node
> Not sure if that order is a definitive one
>
> But to resolve this issue you can try this
> all node probably have the same node weight
> Slurm pick first available node of the minimum node weight

There's a description of this in
https://slurm.schedmd.com/slurm.conf.html#OPT_Weight

> All things being equal, jobs will be allocated the nodes with the lowest weight which satisfies their requirements.

/Ole

--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-leave@lists.schedmd.com