- 07 Jan, 2015 4 commits
-
-
Aaron Knister authored
-
Rémi Palancher authored
Intel MPI, on MPI jobs initialisation through PMI, uses to call PMI_KVS_Put() many many times from task at rank 0, and each on these call is followed by PMI_KVS_Commit(). Slurm implementation of PMI_KVS_Commit() imposes a delay to avoid DDOS on original srun. This delay is proportional to the total number. It could be up to 3 secs for large jobs for ex. with 7168 tasks. Therefore, when Intel MPI calls PMI_KVS_Commit() 475 times (mesured on a test case) from task at rank 0, 28 minutes are spent in delay function. All other tasks in the job are waiting for a PMI_Barrier. Therefore, there is no risk for a DDOS from this single task 0. The patch alters the delaying time calculation to make sure task at rank 0 will does not be delayed. All other tasks are globally spreaded in the same time range as before.
-
Aaron Knister authored
-
Artem Polyakov authored
-
- 05 Jan, 2015 1 commit
-
-
David Bigagli authored
-
- 20 Dec, 2014 1 commit
-
-
Danny Auble authored
-
- 19 Dec, 2014 1 commit
-
-
Danny Auble authored
of Slurm daemons.
-
- 12 Dec, 2014 2 commits
-
-
Danny Auble authored
-
Danny Auble authored
-
- 11 Dec, 2014 3 commits
-
-
Danny Auble authored
If a QOS was added for the job and then removed and it just happened to be the largest QOS id wise if the slurmctld was restarted and the job wasn't flushed out yet it could mess things up.
-
David Bigagli authored
-
Danny Auble authored
accounting_storage/filetxt.
-
- 08 Dec, 2014 1 commit
-
-
Artem Polyakov authored
Logic introdiced in version 14.03.10 to support requeueing of jobs with GRES allocated to currently running steps broke select/linear due to differernces in the plugin logic. The commit with the bad logic is 1209a664
-
- 05 Dec, 2014 1 commit
-
-
Brian Christiansen authored
Bug 1301
-
- 04 Dec, 2014 3 commits
-
-
Brian Christiansen authored
Fix jobs from starting in overlapping reservations that won't finish before a "maint" reservation begins. Bug 1290
-
Danny Auble authored
when the DBD is down.
-
Danny Auble authored
-
- 03 Dec, 2014 2 commits
-
-
Morris Jette authored
This only prints the message if the user enables more detailed logging bug 1171
-
Morris Jette authored
Log Cray MPI job calling exit() without mpi_fini(), but do not treat it as a fatal error. This partially reverts logic added in version 14.03.9. bug 1171
-
- 02 Dec, 2014 3 commits
-
-
Danny Auble authored
better.
-
Danny Auble authored
in BASIL was changed.
-
Brian Christiansen authored
-
- 01 Dec, 2014 1 commit
-
-
Brian Christiansen authored
-
- 24 Nov, 2014 1 commit
-
-
Artem Polyakov authored
Double max string that Slurm can pack from 16MB to 32MB to support larger MPI2 configurations.
-
- 21 Nov, 2014 3 commits
-
-
Danny Auble authored
-
Danny Auble authored
-
Dominik Bartkiewicz authored
This can happen if the specified job ID is not found.
-
- 20 Nov, 2014 2 commits
-
-
David Bigagli authored
cgroup plugin.
-
Morris Jette authored
-
- 18 Nov, 2014 1 commit
-
-
David Bigagli authored
impact functionality.
-
- 13 Nov, 2014 3 commits
-
-
Brian Christiansen authored
Bug 1253
-
Brian Christiansen authored
-
Brian Christiansen authored
Bug 1255
-
- 12 Nov, 2014 2 commits
-
-
Danny Auble authored
-
Morris Jette authored
Do not requeue a batch job from slurmd daemon if it is killed while in the process of being launched (a race condition introduced in v14.03.9). This partially reverts commit 2bc9bc29
-
- 10 Nov, 2014 5 commits
-
-
Danny Auble authored
-
Danny Auble authored
This reverts commit bc7ea952. This ended up causing more issues than it solved, reverting.
-
Danny Auble authored
15.08, but this keeps track of allocated cpus as well as usable cpus: meaning if a user requests --hint=nomultithread they are allocated cpus that aren't usable since they requested to only use the 1st thread on each core. reference bug 1247
-
Danny Auble authored
-
Danny Auble authored
with CR_PACK_NODES. Really do commit d388dd67 a different way to get the same info and be able to lay out tasks correctly when --hint=nomultithread. tests on a 4 core 8 thread system are srun -n6 --hint=nomultithread --exclusive whereami | sort -h srun: cpu count 6 0 snowflake0 - MASK:0x1 1 snowflake0 - MASK:0x2 2 snowflake0 - MASK:0x4 3 snowflake0 - MASK:0x8 4 snowflake1 - MASK:0x1 5 snowflake1 - MASK:0x2 and srun -n10 -N5 --hint=nomultithread --exclusive whereami | sort -h srun: cpu count 10 0 snowflake0 - MASK:0x1 1 snowflake0 - MASK:0x2 2 snowflake0 - MASK:0x4 3 snowflake0 - MASK:0x8 4 snowflake1 - MASK:0x1 5 snowflake1 - MASK:0x2 6 snowflake1 - MASK:0x4 7 snowflake2 - MASK:0x1 8 snowflake3 - MASK:0x1 9 snowflake4 - MASK:0x1
-