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
29fdc31b
Commit
29fdc31b
authored
7 years ago
by
Morris Jette
Browse files
Options
Downloads
Patches
Plain Diff
Clarify when batch script runs on pack job
parent
93589405
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/heterogeneous_jobs.shtml
+9
-4
9 additions, 4 deletions
doc/html/heterogeneous_jobs.shtml
src/slurmctld/proc_req.c
+6
-1
6 additions, 1 deletion
src/slurmctld/proc_req.c
with
15 additions
and
5 deletions
doc/html/heterogeneous_jobs.shtml
+
9
−
4
View file @
29fdc31b
...
...
@@ -95,9 +95,10 @@ containing the line "#SBATCH packjob" as shown below.</p>
<pre>
$ cat new.bash
#!/bin/bash
#SBATCH --cpus-per-task=4 --mem-per-cpu=1
--ntasks=1
28
#SBATCH --cpus-per-task=4 --mem-per-cpu=1
6g
--ntasks=1
#SBATCH packjob
#SBATCH --cpus-per-task=1 --mem-per-cpu=16 --ntasks=1
#SBATCH --cpus-per-task=2 --mem-per-cpu=1g --ntasks=8
srun run.app
$ sbatch new.pash
...
...
@@ -110,10 +111,14 @@ $ cat my.bash
#!/bin/bash
srun run.app
$ sbatch --cpus-per-task=4 --mem-per-cpu=1
--ntasks=1
28
: \
--cpus-per-task=
1
--mem-per-cpu=1
6
--ntasks=
1
my.bash
$ sbatch --cpus-per-task=4 --mem-per-cpu=1
6g
--ntasks=1 : \
--cpus-per-task=
2
--mem-per-cpu=1
g
--ntasks=
8
my.bash
</pre>
<p>The batch script will be executed in the first node in the first component
of the heterogeneous job. For the above example, that will be the job component
with 1 task, 4 CPUs and 64 GB of memory (16 GB for each of the 4 CPUs).</p>
<h2><a name="managing">Managing Jobs</a></h2>
<p>Information maintained in Slurm for a heterogeneous job includes:</p>
...
...
This diff is collapsed.
Click to expand it.
src/slurmctld/proc_req.c
+
6
−
1
View file @
29fdc31b
...
...
@@ -3896,13 +3896,18 @@ static void _slurm_rpc_submit_batch_pack_job(slurm_msg_t *msg)
if
(
error_code
!=
SLURM_SUCCESS
)
goto
send_msg
;
/* Create new job allocations */
submit_job_list
=
list_create
(
NULL
);
_throttle_start
(
&
active_rpc_cnt
);
lock_slurmctld
(
job_write_lock
);
START_TIMER
;
/* Restart after we have locks */
iter
=
list_iterator_create
(
job_req_list
);
while
((
job_desc_msg
=
(
job_desc_msg_t
*
)
list_next
(
iter
)))
{
/* Create new job allocation */
if
(
alloc_only
&&
job_desc_msg
->
script
)
{
info
(
"%s: Pack job %u offset %u has script, being ignord"
,
__func__
,
pack_job_id
,
pack_job_offset
);
xfree
(
job_desc_msg
->
script
);
}
error_code
=
job_allocate
(
job_desc_msg
,
job_desc_msg
->
immediate
,
false
,
NULL
,
alloc_only
,
uid
,
&
job_ptr
,
...
...
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