Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Slurm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tud-zih-energy
Slurm
Commits
cbe2380a
Commit
cbe2380a
authored
7 years ago
by
Alejandro Sanchez
Browse files
Options
Downloads
Patches
Plain Diff
Docs - better reword the resource limits note added in
2ef56d4b
.
Bug 4681.
parent
068ed34a
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/html/resource_limits.shtml
+8
-4
8 additions, 4 deletions
doc/html/resource_limits.shtml
with
8 additions
and
4 deletions
doc/html/resource_limits.shtml
+
8
−
4
View file @
cbe2380a
...
@@ -31,10 +31,14 @@ Consider the following example:</p>
...
@@ -31,10 +31,14 @@ Consider the following example:</p>
<p>The limits in effect will be MaxJobs=20 and MaxSubmitJobs=50.</p>
<p>The limits in effect will be MaxJobs=20 and MaxSubmitJobs=50.</p>
<p>Note: The precedence order specified above is respected except for the
<p>Note: The precedence order specified above is respected except for the
following limits: Max[Time|Wall], [Min|Max]Nodes. For these limits, the
following limits: Max[Time|Wall], [Min|Max]Nodes. For these limits, even
Partition limit takes precedence over the rest, unless the job's QOS is has
if the job is enforced with QOS and/or Association limits, it can't
the respective PartitionTimeLimit and/or Partition[Max|Min]Nodes, which would
go over the limit imposed at Partition level, even if it listed at the bottom.
reverse the precedence order.
So the default for these 3 types of limits is that they are upper bound by the
Partition one. This Partition level bound can be ignored if
the respective QOS PartitionTimeLimit and/or Partition[Max|Min]Nodes flags
are set, then the job would be enforced the limits imposed at QOS
and/or association level respecting the order above.
</p>
</p>
<h2>Configuration</h2>
<h2>Configuration</h2>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment