Try "squeue --start". That shows expected start times for jobs. Those
times are not necessarily available immediately, but after the
backfill scheduler runs (with a typical configuration). The expected
allocated resources are not available, only the times.
Quoting Martins Innus <[email protected]>:
Moe,
This patch looks like it would be very useful. Would it be
possible to have this information available in squeue? That is, be
able to see what nodes a job is currently expected to start on
without digging into the logs.
Thanks
Martins
On 10/11/13 12:22 PM, Moe Jette wrote:
See "DebugFlags=debug". What that prints today is a map through
time of what resources are NOT already reserved for pending jobs. I
just added some logging that will make the information easier for
you to use, showing when and where the backfill scheduler is trying
to start jobs. It will be much easier for you to follow what is
happening if you add the patch here:
https://github.com/SchedMD/slurm/commit/260eed9b45358fbb17a9f7b98a5135c6f733f9c4 Quoting Ulf Markwardt
<[email protected]>:
On 10.10.2013 17:58, Moe Jette wrote:
The backfill scheduler does not change the state of any jobs (other than
the once it starts). If there is a high priority job in the queue, the
lower priority jobs will retain a reason of "Priority" unless it can not
be started due to some limit, down nodes, etc.
Having more accurate job time limits can help with backfill scheduling.
One thing that some sites do is require that the user explicitly specify
a job time limit.
Dear Moe,
how can I see the work of the backfill scheduler e.g. with some
(?) debug option. If I want to change the backfill parameters I
would like to have an "observable" to evaluate my modifications.
Thank you,
Ulf
