After assistance from an AWS colleague, GrpTRESMins seems to be working.
Hoot
> On Apr 21, 2023, at 4:43 AM, Ole Holm Nielsen
> wrote:
>
> Hi Jason,
>
> On 4/20/23 20:11, Jason Simms wrote:
>> Hello Ole and Hoot,
>> First, Hoot, thank you for your question. I've managed Slurm for a few years
Hi Jason,
On 4/20/23 20:11, Jason Simms wrote:
Hello Ole and Hoot,
First, Hoot, thank you for your question. I've managed Slurm for a few
years now and still feel like I don't have a great understanding about
managing or limiting resources.
Ole, thanks for your continued support of the user
Hello Ole and Hoot,
First, Hoot, thank you for your question. I've managed Slurm for a few
years now and still feel like I don't have a great understanding about
managing or limiting resources.
Ole, thanks for your continued support of the user community with your
documentation. I do wish not onl
So an update, GrpTRES registers a value while a job is running but GRpTRESMins
does not. So I still have something wrong. GrpTRESMins reads in the docs like
it is in fact an aggregate number.
> On Apr 20, 2023, at 1:01 PM, Ole Holm Nielsen
> wrote:
>
> On 20-04-2023 18:23, Hoot Thompson wrote
And it indeed does show current value for a running job!! Do I feel stupid :-)
> On Apr 20, 2023, at 1:01 PM, Ole Holm Nielsen
> wrote:
>
> On 20-04-2023 18:23, Hoot Thompson wrote:
>> Ole,
>> Earlier I found your Slurm_tools posting and found it very useful. This
>> remains my problem, ‘cur
Ah, I thought that was the aggregate of past and current jobs.
> On Apr 20, 2023, at 1:01 PM, Ole Holm Nielsen
> wrote:
>
> On 20-04-2023 18:23, Hoot Thompson wrote:
>> Ole,
>> Earlier I found your Slurm_tools posting and found it very useful. This
>> remains my problem, ‘current value’
On 20-04-2023 18:23, Hoot Thompson wrote:
Ole,
Earlier I found your Slurm_tools posting and found it very useful. This
remains my problem, ‘current value’ not incrementing even after making
needed changes to slurm.conf.
The ‘current value’ refers to those jobs that are currently running.
Do
Ole,
Earlier I found your Slurm_tools posting and found it very useful. This remains
my problem, ‘current value’ not incrementing even after making needed changes
to slurm.conf.
./showuserlimits -u ubuntu
scontrol -o show assoc_mgr users=ubuntu account=testing flags=Assoc
Association (Parent a
Thank you for this. I’ll give it a read but no promises that I won’t be back
with more questions!
Hoot
> On Apr 20, 2023, at 2:10 AM, Ole Holm Nielsen
> wrote:
>
> Hi Hoot,
>
> On 4/20/23 00:15, Hoot Thompson wrote:
>> Is there a ‘how to’ or recipe document for setting up and enforcing resou
Hi Hoot,
On 4/20/23 00:15, Hoot Thompson wrote:
Is there a ‘how to’ or recipe document for setting up and enforcing resource
limits? I can establish accounts, users, and set limits but 'current value' is
not incrementing after running jobs.
I have written about resource limits in this Wiki p
Is there a ‘how to’ or recipe document for setting up and enforcing resource
limits? I can establish accounts, users, and set limits but 'current value' is
not incrementing after running jobs.
Thanks in advance
I am having an issue with limits not being enforced if I set
`AccountingStorageEnforce=limits,qos`, is this as expected? It allows
any user to submit jobs as well even if they do not have an
association. Seems to apply the default qos to every job but then
ignores associations and per user/account
Hello all,
As I understand the resource limits is applied as follow:
1. Partition QOS limit
2. Job QOS limit
3. User association
4. Account association(s), ascending the hierarchy
5. Root/Cluster association
6. Partition limit
7. None
Here I set the limit on the cluster association-
sacctmgr mod
13 matches
Mail list logo
