pedmon at cfa.harvard.edu
Tue Jul 6 13:20:42 UTC 2021
The documentation indicates that's what should happen with 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
resources. The default value is 300 seconds. A value of zero
prevents any job record purging. Jobs are not purged during a
backfill cycle, so it can take longer than MinJobAge seconds to
purge a job if using the backfill scheduling plugin. In order to
eliminate some possible race conditions, the minimum non-zero value
for *MinJobAge* recommended is 2.
From my experience this does work. We've been running with
MinJobAge=600 for years with out any problems to my knowledge
On 7/6/2021 8:59 AM, Emre Brookes wrote:
>> Brian Andrus
>> Nov 23, 2020, 1:55:54 PM
>> to slurm... at lists.schedmd.com
>> 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 completed state for a period of time,
>> but they are not showing up at all on our cluster.
>> How does one have jobs show up that are completed?
> 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?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the slurm-users