Re: [slurm-users] srun and Intel MPI 2020 Update 4

On 11/5/20 4:41 PM, Ciaron Linstead wrote: I've been trying to run a simple MPI application (the Intel MPI Benchmark) using the latest Intel Parallel Studio (2020 Update 4) and srun. Version 2019 Update 4 runs this example correctly, as does mpirun. SLURM is 17.11.7 The error I get is the fol

[slurm-users] qos.html - "will affect the job in three ways"

https://slurm.schedmd.com/qos.html qos.html has at the beginning "... will affect the job in three ways" but then lists 5 items. Should this be edited? Youssef Eldakar Bibliotheca Alexandrina

[slurm-users] sacct output issue with -s specification

Hi, Appreciate some insight/help on sacct issue: I have been dumping output for finished jobs using the following and on v18, suddenly the same '-s' option is not producing any output: * On version 17.11.10, I get valid output. $ sacct -a -s F,CD -S 2020-10-01 13398 Job25.1

Re: [slurm-users] update_node / reason set to: slurm.conf / state set to DRAINED

Hi Kevin, On 11/4/20 6:00 pm, Kevin Buckley wrote: In looking at the SlurmCtlD log we see pairs of lines as follows  update_node: node nid00245 reason set to: slurm.conf  update_node: node nid00245 state set to DRAINED I'd go looking in your healthcheck scripts, I took a quick look at the

[slurm-users] srun and Intel MPI 2020 Update 4

Hello all I've been trying to run a simple MPI application (the Intel MPI Benchmark) using the latest Intel Parallel Studio (2020 Update 4) and srun. Version 2019 Update 4 runs this example correctly, as does mpirun. SLURM is 17.11.7 The error I get is the following, unless I use --exclusive

Re: [slurm-users] update_node / reason set to: slurm.conf / state set to DRAINED

Hi Kevin, I have no experience with version 20 of slurm, but probably you have some misconfiguration. Have you changed any settings in your slurm.conf file after the upgrade? Dive into the documentation and verify if there aren't any changes to some of the directives within the slurm.conf. On

Re: [slurm-users] Using hyperthreaded processors

Le mercredi 04 novembre 2020 à 21:41 +, Sebastian T Smith a écrit : > Hi, Hi, > We have Hyper-threading/SMT enabled on our cluster. It's challenging > to fully utilize threads, as Brian suggests. We have a few workloads > that benefit from it being enabled Our cluster services tasks in the

[slurm-users] sacct output issue with -s specification

Hi, I have been dumping output for finished jobs using the following and on v18, suddenly the same '-s' option is not producing any oputput: $ sacct -a -s F,CD -S 2020-10-01 13398 Job25.1 defq32 FAILED 9:0 13398.batch batch