Hi Brian,
Thanks for the response!
However, this particular approach where we need to accept whatever slurm gives us as starting node
and deal with it accordingly doesn’t work for us.

I think there should be flexibility in slurm to switch the starting node as requested,
through some C API. This is possible in other scheduling system like LSF.

Any other way to do this with the current slurm code base is welcome.

Regards,
Bhaskar.


Sent from Yahoo Mail for iPad

On Friday, November 1, 2024, 1:12 AM, Brian Andrus via slurm-users <slurm-users@lists.schedmd.com> wrote:

Likely many ways to do this, but if you have some code that is dependent on something, that check could be in the code itself.

So instead of process 0 being the required process to run, it would be whichever process meets the requirements.

eg:

case hostname:
harold)
    Run harold's stuff here
*)
    Run all other stuff here
esac

Takes some coding effort but keeps control of the processes within your own code.

Brian Andrus

On 10/30/24 09:35, Bhaskar Chakraborty via slurm-users wrote:
Hi,

Is there a way to change/control the primary node (i.e. where the initial task starts) as part of a job's allocation.

For eg, if a job requires 6 CPUs & its allocation is distributed over 3 hosts h1, h2 & h3 I find that it always starts the task in 1 particular
node (say h1) irrespective of how many slots were available in the hosts.

Can we somehow let slurm have the primary node as h2?

Is there any C-API inside select plugin which can do this trick if we were to control it through the configured select plugin?

Thanks.
-Bhaskar.


    
  

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