Ward Poelmans wrote:
On 6/07/2021 14:59, Emre Brookes wrote:
I'm using slurm 20.02.7 & have the same issue (except I am running batch jobs).
Does MinJobAge work to keep completed jobs around for the specified duration in
squeue output?
It does for me if I do 'squeue -t all'. This is slurm 20.1
On 6/07/2021 14:59, Emre Brookes wrote:
> I'm using slurm 20.02.7 & have the same issue (except I am running batch
> jobs).
> Does MinJobAge work to keep completed jobs around for the specified duration
> in squeue output?
It does for me if I do 'squeue -t all'. This is slurm 20.11.7.
Ward
The documentation indicates that's what should happen with MinJobAge:
*MinJobAge*
The minimum age of a completed job before its record is purged from
Slurm's active database. Set the values of *MaxJobCount* and to
ensure the slurmctld daemon does not exhaust its memory or other
resour
Brian Andrus
Nov 23, 2020, 1:55:54 PM
to slurm...@lists.schedmd.com
All,
I always thought that MinJobAge affected how long a job will show up
when doing 'squeue'
That does not seem to be the case for me.
I have MinJobAge=900, but if I do 'squeue --me' as soon as I finish an
interactive
All,
I always thought that MinJobAge affected how long a job will show up
when doing 'squeue'
That does not seem to be the case for me.
I have MinJobAge=900, but if I do 'squeue --me' as soon as I finish an
interactive job, there is nothing in the queue.
I swear I used to see jobs in a com
Using slurm 19.05.0-1
MinJobAge is set to 300
MaxJobCount is set to 1
There are only about 30 jobs running. However, when a job completes, it
vanishes immediately from the output of 'squeue'
Shouldn't it be staying there for 5 minutes?
Brian Andrus
