Marcin,
Thanks for the bindtmp link. Reading the code, I note it looks for
/etc/passwd. We are using sssd for auth - I presume that means this plugin
will not work for us?
cheers
L.
--
The most dangerous phrase in the language is, "We've always done it this
way."
- Grace Hopper
On 27 June
On 23/08/16 01:24, Ulf Markwardt wrote:
> I really want the bf scheduler to step down to the lowest priority -
> every once in a while.
Isn't this what bf_continue is for?
bf_continue
The backfill scheduler periodically releases locks in order
to permit other operations to proceed rather
The standard registration option for for the 2016 Slurm User Group
meeting will end on August 31. If you plan on attending the Slurm user
group meeting please sign up soon.
* https://slug2016.eventbrite.com
* http://slurm.schedmd.com/slurm_ug_agenda.html
Regards,
Jacob
Daniel,
> You may want to take a look at adjusting bf_max_job_test and depending
> on your typical runtime for jobs increasing bf_resolution to combat an
> increase in overhead.
I know I can limit the number of jobs the bf scheduler looks at with
bf_max_job_... parameters.
My question is not
Hi Ulf,
You may want to take a look at adjusting bf_max_job_test and depending
on your typical runtime for jobs increasing bf_resolution to combat an
increase in overhead.
On 08/22/2016 10:24 AM, Ulf Markwardt wrote:
> Dear all,
>
> how can I bring the backfill scheduler to examine all
Dear all,
how can I bring the backfill scheduler to examine all low-priority jobs
for possible execution?
We have situations with >10 jobs and times with just a few hundreds.
So a fixed bf_interval does not make sense.
Is there some option to say the bf scheduler runs down to the bottom of
Il 12/08/2016 01:42, Christopher Samuel ha scritto:
> The CR_ONE_TASK_PER_CORE is a hold over from then, it means that if
> you've got HT/SMT enabled you'll get one MPI rank (Slurm task) per
> physical core and that can then use threads to utilise the hardware
> thread units. Without it you'll
