I suspect it is the order of registration.

So, even if you unregister a node, it still exists internally. Even if you delete the node, it would still be in the db with a 'deleted' flag. I haven't dug into the code to validate, but that is what I have gone with and it hasn't been off for me.


Brian Andrus


On 10/22/2025 6:13 AM, Assmann, Greta Marie via slurm-users wrote:
Dear Patrick and Ole,

Thanks a lot for your fast answers!

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: [email protected]

------------------------------------------------------------------------
*From:* Ole Holm Nielsen via slurm-users <[email protected]>
*Sent:* 22 October 2025 15:02
*To:* [email protected] <[email protected]>
*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 -- [email protected]
To unsubscribe send an email to [email protected]
-- 
slurm-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to