This is maybe a little of topic but I saw some posts in this list about slurm
installations. We at SURF(sara) have developed a services framework for
CFEngine3 that
install/configure/maintain with the aid of templates(mustache) and json files.
Everything can be configured with external data
Thanks Renfro. My scheduling policy is below.
SchedulerType=sched/builtin
SelectType=select/cons_res
SelectTypeParameters=CR_Core
AccountingStorageEnforce=associations
AccountingStorageHost=192.168.150.223
AccountingStorageType=accounting_storage/slurmdbd
ClusterName=hpc
“The SchedulerType configuration parameter specifies the scheduler plugin to
use. Options are sched/backfill, which performs backfill scheduling, and
sched/builtin, which attempts to schedule jobs in a strict priority order
within each partition/queue.”
Hello,
I would like to know if "preempt_reorder_count=#" is really used when using
"preempt_strict_order".
In my understanding:
* "preempt_reorder_count=#" sets the number of iterations to reorder the
preemption job list based on the job size. Allows to minimize the number of
preempted
Hi Team,
We have separate partitions for the GPU nodes and only CPU nodes .
scenario: the jobs submitted in our environment is 4CPU+1GPU as well as
4CPU only in nodeGPUsmall and nodeGPUbig. so when all the GPU exhausted
and rest other jobs are in queue waiting for the availability of GPU
Hi Janna,
If you're running an old Slurm version, there may be bugs already resolved
in the later versions. You can search for bugs with ReqNodeNotAvail in
the title:
https://bugs.schedmd.com/buglist.cgi?quicksearch=ReqNodeNotAvail
For example, this one might be relevant:
