We are pleased to announce the availability of Slurm version 20.02.2.
This includes a series of moderate and minor fixes since the last
maintenance releases for both branches.
Slurm can be downloaded from https://www.schedmd.com/downloads.php .
- Tim
--
Tim Wickberg
Chief Technology Officer,
Well looking at the current slurm.conf it appears that the name was
changed, and "Shared" is now called "OverSubscribe" in more modern slurm
versions. So you might look deeper at what config options are in
conflict, since with the EXCLUSIVE mode I get one node per job here.
Allan
Allan Streib wr
I'm running an even older slurm than you (it does what I need, I am a
team of one and I have many things to take care of other than chasing
the latest version of every piece of software).
Anyway, did you try Shared=EXCLUSIVE in the partition configuration?
>From the (v14.11.7) slurm.conf man page
We use the elasticsearch plugin. This information is kept in there.
From: slurm-users on behalf of Gestió
Servidors
Sent: Thursday, April 30, 2020 3:39:33 AM
To: slurm-users@lists.schedmd.com
Subject: [slurm-users] How to get command from a finished job
Hello,
On 30-04-2020 15:34, Bjørn-Helge Mevik wrote:
Gestió Servidors writes:
For example, with "scontrol show jobid" I can know what command has
been submited, its workir, the stderr file and the stdout one. This
information, I think, cannot be obtained when the job is finished and
I run "sacct".
Gestió Servidors writes:
> For example, with "scontrol show jobid" I can know what command has
> been submited, its workir, the stderr file and the stdout one. This
> information, I think, cannot be obtained when the job is finished and
> I run "sacct".
The workdir is available with sacct, IIRC.
You can adjust or enforce almost anything about a job with a job_submit.lua [1
(search for “JobSubmitPlugins”), 2].
Assuming you want this node in a single partition, you can set ExclusiveUser in
a partition definition in slurm.conf. That would at least keep other users off
the node, but wouldn
Hi there,
On 4/30/20 2:52 PM, Paul Edmon wrote:
> No, that data is purged from the scheduler after completion. So records of
> the job exist in your job completion log or in the sacct database. The
> script that it ran is not saved, though I believe there are several bug
> requests in to Sche
No, that data is purged from the scheduler after completion. So records
of the job exist in your job completion log or in the sacct database.
The script that it ran is not saved, though I believe there are several
bug requests in to SchedMD to add that feature. People have come up
with vario
I did some tests and this doesn't work with MPI, in the following sense:
the way we were running parallel jobs was by invoking `sbatch -n4
script.sh` where the script.sh would contain an `mpirun` command without
specifying the number of processors. It would then simply claim the ones
assigned to it
This seems like the easiest solution, but how would that interact with MPI
jobs? Apologies if these are really basic questions, and thank you very
much for thinking along.
Rutger
On Wed, Apr 29, 2020 at 10:25 PM Doug Meyer wrote:
> Change node definition in slurm.conf for that one node to 1 CPU
Hello,
I would like to know if there exist any way to get the same information I can
get from a running or pending job in the queue with "scontrol show jobid="
when the job has finished. When it has finished, "scontrol show jobid="
doesn't work and "sacct -j jobid" doesn't show all the
12 matches
Mail list logo
