[slurm-users] squeue: compact pending job-array in one partition, but not in other

79 views
Skip to first unread message

Loris Bennett

unread,
Feb 23, 2021, 2:00:29 PM2/23/21
to Slurm Users Mailing List
Hi,

Does anyone have an idea why pending elements of an array job in one
partition should be displayed compactly by 'squeue' but those of another
in a different partition are displayed one element per line? Please see below
(compact display in 'main', one element per line in 'scavenger').
This is with version 20.02.6

Cheers,

Loris

JOBID PARTITION ST TIME NODES NODELIST(REASON)
...
6755576 main PD 0:00 1 (Priority)
6749327_[754-1000] main PD 0:00 1 (Priority)
6748246 main PD 0:00 1 (Priority)
6749213 main PD 0:00 1 (Priority)
6749309 main PD 0:00 1 (Priority)
6750124 main PD 0:00 1 (Priority)
6752967 main PD 0:00 1 (Priority)
6746767 main PD 0:00 1 (Priority)
6755188 main PD 0:00 1 (Priority)
6702557_[13] main PD 0:00 4 (Priority)
6702858_[1-10] main PD 0:00 4 (Priority)
6703700_[1-4,6-8] main PD 0:00 4 (Priority)
6703764_[1] main PD 0:00 4 (Priority)
6705324_[1,3,5,9] main PD 0:00 4 (Priority)
6748962 main PD 0:00 4 (Priority)
6709963 main PD 0:00 1 (Priority)
6709964 main PD 0:00 1 (Priority)
6709976 main PD 0:00 1 (Priority)
6462709_[1-77,79-8 main PD 0:00 1 (QOSMaxCpuPerUserLimit)
6463366_[1-2,28-72 main PD 0:00 1 (QOSMaxCpuPerUserLimit)
6577272_21 scavenger PD 0:00 1 (Priority)
6577272_22 scavenger PD 0:00 1 (Priority)
6577272_23 scavenger PD 0:00 1 (Priority)
6577272_28 scavenger PD 0:00 1 (Priority)
--
Dr. Loris Bennett (Hr./Mr.)
ZEDAT, Freie Universität Berlin Email loris....@fu-berlin.de

Jeffrey T Frey

unread,
Feb 23, 2021, 2:09:00 PM2/23/21
to Slurm User Community List
Did those four jobs


6577272_21 scavenger PD 0:00 1 (Priority)
6577272_22 scavenger PD 0:00 1 (Priority)
6577272_23 scavenger PD 0:00 1 (Priority)
6577272_28 scavenger PD 0:00 1 (Priority)


run before and get requeued? Seems likely with a partition named "scavenger."

Loris Bennett

unread,
Feb 24, 2021, 1:42:40 AM2/24/21
to Slurm User Community List
Hi Jeffrey,

Yes, those jobs (and elements of other array which were also
listed one per line) had indeed been preempted and requeued.

So is this behaviour intended/documented or is it a bug?

Cheers,

Loris

Thomas M. Payerle

unread,
Feb 24, 2021, 9:15:56 AM2/24/21
to Slurm User Community List
I believe this behavior is intended as various properties of the jobs that were requeued no longer match the properties of the rest of the job array.  It might not show on the minimal output you are displaying, but I suspect the jobs were requeued at different times and so the priorities of the jobs (which typically increases with time spent in the queue) are no longer identical.
--
Tom Payerle
DIT-ACIGS/Mid-Atlantic Crossroads        pay...@umd.edu
5825 University Research Park               (301) 405-6135
University of Maryland
College Park, MD 20740-3831
Reply all
Reply to author
Forward
0 new messages