On Sun, Nov 3, 2019 at 7:18 AM Juergen Salk wrote:
>
> Hi,
>
> maybe I missed it, but what does squeue say in the reason field for
> your pending jobs that you expect to slip in?
>
>
the reason on these jobs is just "Priority".
> Is your partition maybe configured for exclusive node access,
Hi,
maybe I missed it, but what does squeue say in the reason field for
your pending jobs that you expect to slip in?
Is your partition maybe configured for exclusive node access, e.g. by
setting `OverSubscribe=EXCLUSIVE´?
Best regards
Jürgen
--
Jürgen Salk
Scientific Software & Compute
I see - yes, to clarify, we are specifying memory for each of these jobs,
and there is enough memory on the nodes for both types of jobs to be
running simultaneously.
On Fri, Nov 1, 2019 at 1:59 PM Brian Andrus wrote:
> I ask if you are specifying it, because if not, slurm will assume a job
>
: Friday, November 1, 2019 at 11:09 AM
To: Slurm User Community List
Subject: Re: [slurm-users] job priority keeping resources from being used?
On my low resource jobs I'm setting the time to 1 hour, and on my large ones
I'm setting time=unlimited.
Is the unlimited part the problem? I have
I ask if you are specifying it, because if not, slurm will assume a job
will use all the memory available.
So without specifying, your big job gets allocated 100% of the memory so
nothing could be sent to the node. Same if you don't specify for the
little jobs. It would want 100%, but if
yes, there is enough memory for each of these jobs, and there is enough
memory to run the high resource and low resource jobs at the same time.
On Fri, Nov 1, 2019 at 1:37 PM Brian Andrus wrote:
> Are you specifying memory for each of the jobs?
>
> Can't run a small job if there isn't enough
Are you specifying memory for each of the jobs?
Can't run a small job if there isn't enough memory available for it.
Brian Andrus
On 11/1/2019 7:42 AM, c b wrote:
I have:
SelectType=select/cons_res
SelectTypeParameters=CR_CPU_Memory
On Fri, Nov 1, 2019 at 10:39 AM Mark Hahn
;> *From: *slurm-users on behalf of
>> c b
>> *Reply-To: *Slurm User Community List
>> *Date: *Friday, November 1, 2019 at 10:30 AM
>> *To: *"slurm-users@lists.schedmd.com"
>> *Subject: *[slurm-users] job priority keeping resources from being used?
>&g
:30 AM
> *To: *"slurm-users@lists.schedmd.com"
> *Subject: *[slurm-users] job priority keeping resources from being used?
>
>
>
> [WARNING: External Email - Use Caution]
>
>
>
> Hi,
>
>
>
> Apologies for the weird subject line...I don't know how
Community List
Date: Friday, November 1, 2019 at 10:30 AM
To: "slurm-users@lists.schedmd.com"
Subject: [slurm-users] job priority keeping resources from being used?
[WARNING: External Email - Use Caution]
Hi,
Apologies for the weird subject line...I don't know how else to describe what
I have:
SelectType=select/cons_res
SelectTypeParameters=CR_CPU_Memory
On Fri, Nov 1, 2019 at 10:39 AM Mark Hahn wrote:
> > In theory, these small jobs could slip in and run alongside the large
> jobs,
>
> what are your SelectType and SelectTypeParameters settings?
> ExclusiveUser=YES on
Hi,
Apologies for the weird subject line...I don't know how else to describe
what I'm seeing.
Suppose my cluster has machines with 8 cores each. I have many large high
priority jobs that each require 6 cores, so each machine in my cluster runs
one of each of these jobs at a time. However, I
12 matches
Mail list logo