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
9a21a393
Commit
9a21a393
authored
23 years ago
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
Add clarifications and additional information for configurations with
respect to scheduling issues. - Jette
parent
ccf8b639
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/html/admin.guide.html
+12
-3
12 additions, 3 deletions
doc/html/admin.guide.html
doc/html/programmer.guide.html
+1
-1
1 addition, 1 deletion
doc/html/programmer.guide.html
with
13 additions
and
4 deletions
doc/html/admin.guide.html
+
12
−
3
View file @
9a21a393
...
...
@@ -153,11 +153,16 @@ Weight is an integer value with a default value of 1.
<p>
Only the NodeName must be supplied in the configuration file; all other
items are optional.
It is advisable to establish baseline node configurations in
the configuration
file, especially if the cluster is heterogeneous.
It is advisable to establish baseline node configurations in
the configuration
file, especially if the cluster is heterogeneous.
Nodes which register to the system with less than the configured resources
(e.g. too little memory), will be placed in the "DOWN" state to
avoid scheduling jobs on them.
Establishing baseline configurations will also speed SLURM's
scheduling process by permitting it to compare job requirements
against these (relatively few) configuration parameters and
possibly avoid having to perform checks job requirements
against every individual node's configuration.
The resources checked at node registration time are: CPUs,
RealMemory and TmpDisk.
While baseline values for each of these can be established
...
...
@@ -407,6 +412,10 @@ may not be changed by slurm_admin.
<dd>
State of the job. Possible values are "PENDING", "STARTING",
"RUNNING", and "ENDING".
<dt>
Shared
<dd>
Job can share nodes with other jobs. Possible values are 1
and 0 for YES and NO respectively.
<dt>
User
<dd>
Name of the user executing this job.
...
...
@@ -607,7 +616,7 @@ Remove node lx30 from service, removing jobs as needed:
<hr>
URL = http://www-lc.llnl.gov/dctg-lc/slurm/admin.guide.html
<p>
Last Modified March 1
3
, 2002
</p>
<p>
Last Modified March 1
5
, 2002
</p>
<address>
Maintained by
<a
href=
"mailto:slurm-dev@lists.llnl.gov"
>
slurm-dev@lists.llnl.gov
</a></address>
</body>
...
...
This diff is collapsed.
Click to expand it.
doc/html/programmer.guide.html
+
1
−
1
View file @
9a21a393
...
...
@@ -20,7 +20,7 @@ for Resource Management</a>.
<h2>
Common Modules
</h2>
This directory contains modules of general use throughout the SLURM cod.
This directory contains modules of general use throughout the SLURM cod
e
.
The modules are described below.
<dl>
...
...
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