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
aad57635
Commit
aad57635
authored
19 years ago
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
Add faq info on shared nodes.
parent
33167684
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/faq.shtml
+16
-1
16 additions, 1 deletion
doc/html/faq.shtml
with
16 additions
and
1 deletion
doc/html/faq.shtml
+
16
−
1
View file @
aad57635
...
@@ -18,6 +18,7 @@ found on a node rather than what is defined in <i>slurm.conf</i>?</a></li>
...
@@ -18,6 +18,7 @@ found on a node rather than what is defined in <i>slurm.conf</i>?</a></li>
<li><a href="#return_to_service">Why is a node shown in state DOWN when the node
<li><a href="#return_to_service">Why is a node shown in state DOWN when the node
has registered for service?</a></li>
has registered for service?</a></li>
<li><a href="#down_node">What happens when a node crashes?</a></li>
<li><a href="#down_node">What happens when a node crashes?</a></li>
<li><a href="#share">How can I control the execution of multiple jobs per node?</a></li>
</ol>
</ol>
<p><a name="comp"><b>1. Why is my job/node in COMPLETING state?</b></a><br>
<p><a name="comp"><b>1. Why is my job/node in COMPLETING state?</b></a><br>
When a job is terminating, both the job and its nodes enter the state "completing."
When a job is terminating, both the job and its nodes enter the state "completing."
...
@@ -212,6 +213,20 @@ with the srun option <i>--no-kill</i>.
...
@@ -212,6 +213,20 @@ with the srun option <i>--no-kill</i>.
Any active job step on that node will be killed.
Any active job step on that node will be killed.
See the slurm.conf and srun man pages for more information.</p>
See the slurm.conf and srun man pages for more information.</p>
<p style="text-align:center;">Last modified 18 January 2006</p>
<p><a name="share"><b>13. How can I control the execution of multiple
jobs per node?</b></a><br>
There are two mechanism to control this.
If you want to allocate individual processors on a node to jobs,
configure <i>SelectType=select/cons_res</i>.
See <a href="cons_res.html">Consumable Resources in SLURM</a>
for details about this configuration.
If you want to allocate whole nodes to jobs, configure
configure <i>SelectType=select/linear</i>.
Each partition also has a configuration parameter <i>Shared</i>
that enables more than one job to execute on each node.
See <i>man slurm.conf</i> for more information about these
configuration paramters.</p>
<p style="text-align:center;">Last modified 22 February 2006</p>
<!--#include virtual="footer.txt"-->
<!--#include virtual="footer.txt"-->
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