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
1361f31e
Commit
1361f31e
authored
16 years ago
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
explain how premature exit if one task of a parallel job is handled
parent
8cac7490
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
+15
-1
15 additions, 1 deletion
doc/html/faq.shtml
with
15 additions
and
1 deletion
doc/html/faq.shtml
+
15
−
1
View file @
1361f31e
...
...
@@ -23,6 +23,8 @@ name for a batch job?</a></li>
allocated to a SLURM job?</a></li>
<li><a href="#terminal">Can tasks be launched with a remote terminal?</a></li>
<li><a href="#force">What does "srun: Force Terminated job" indicate?</a></li>
<li><a href="#early_exit">What does this mean: "srun: First task exited 30s ago"
followed by "srun Job Failed"?</a></li>
</ol>
<h2>For Administrators</h2>
<ol>
...
...
@@ -463,6 +465,18 @@ If the job step's I/O does not terminate in a timely fashion
thereafter, pending I/O is abandoned and the srun command
exits.</p>
<p><a name="early_exit"><b>17. What does this mean:
"srun: First task exited 30s ago"
followed by "srun Job Failed"?</b></a><br>
The srun command monitors when tasks exit. By default, 30 seconds
after the first task exists, the job is killed.
This typically indicates some type of job failure and continuing
to execute a parallel job when one of the tasks has exited is
not normally productive. This behavior can be changed using srun's
<i>--wait=<time></i> option to either change the timeout
period or disable the timeout altogether. See srun's man page
for details.
<p class="footer"><a href="#top">top</a></p>
<h2>For Administrators</h2>
...
...
@@ -933,6 +947,6 @@ slurmdbd.
<p class="footer"><a href="#top">top</a></p>
<p style="text-align:center;">Last modified 1 May 2008</p>
<p style="text-align:center;">Last modified 1
3
May 2008</p>
<!--#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