Hmmm... the man page says of "reduce_completing_frag,"
"By default if a job is found completing then no jobs are scheduled. If
this parameter is used the node in a completing job are taken out of
consideration."
This feels like it's missing a word or two. The first sentence says
that, by def
Thanks Kilian!
On 04/16/2018 02:15 PM, Kilian Cavalotti wrote:
Hi Andy,
On Mon, Apr 16, 2018 at 8:43 AM, Andy Riebs wrote:
I hadn't realized that jobs can be scheduled to run on a node that is still
in "completing" state from an earlier job. We occasionally use epilog
scripts that can take 3
Hi Andy,
On Mon, Apr 16, 2018 at 8:43 AM, Andy Riebs wrote:
> I hadn't realized that jobs can be scheduled to run on a node that is still
> in "completing" state from an earlier job. We occasionally use epilog
> scripts that can take 30 seconds or longer, and we really don't want the
> next job t
I hadn't realized that jobs can be scheduled to run on a node that is
still in "completing" state from an earlier job. We occasionally use
epilog scripts that can take 30 seconds or longer, and we really don't
want the next job to start until the epilog scripts have completed.
Other than codin
