Skip to content
Snippets Groups Projects
Commit cbe2380a authored by Alejandro Sanchez's avatar Alejandro Sanchez
Browse files

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
...@@ -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>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment