- 20 Mar, 2015 1 commit
-
-
Morris Jette authored
If SchedulerParameters value of bf_min_age_reserve is configured, then a newly submitted job can start immediately even if there is a higher priority non-runnable job which has been waiting for less time than bf_min_age_reserve.
-
- 19 Mar, 2015 2 commits
-
-
Morris Jette authored
-
Morris Jette authored
-
- 18 Mar, 2015 7 commits
-
-
jette authored
Start job allocation using lowest numbered sockets for block task distribution for consistency with cyclic distribution. bug 1540
-
Danny Auble authored
block is set up to it's original state.
-
jette authored
Add the ability for a compute node to be allocated to multiple jobs, but restricted to a single user. Added "--exclusive=user" option to salloc, sbatch and srun commands. Added "owner" field to node record, visible using the scontrol and sview commands. Added new partition configuration parameter "ExclusiveUser=yes|no". Add "Shared=user" job state information.
-
Brian Christiansen authored
-
Brian Christiansen authored
Bug 1533
-
jette authored
Fix bug that can permit someone to kill job array belonging to another user.
-
jette authored
Fix support for --mem=0 (all memory of a node) with select/cons_res plugin. Previously the job would not have it's memory constrained, but it would not make that memory unavailable to other jobs either. bug 1526
-
- 17 Mar, 2015 1 commit
-
-
Aaron Knister authored
This was previously added to v14.11
-
- 16 Mar, 2015 1 commit
-
-
jette authored
Added new SchedulerParameters value of bf_min_age_reserve. The backfill scheduler will not reserve resources for pending jobs until they have been pending for at least the specified number of seconds. This can be valuable if jobs lack time limits or all time limits have the same value.
-
- 13 Mar, 2015 2 commits
-
-
Morris Jette authored
Increase maximum MaxArraySize configuration parameter value from 1,000,001 to 4,000,001. bug 1535
-
David Bigagli authored
-
- 12 Mar, 2015 2 commits
-
-
Marlys Kohnke authored
-
Morris Jette authored
Added LaunchParameters configuration parameter. Have srun command test locally for the executable file if LaunchParameters=test_exec or the environment variable SLURM_TEST_EXEC is set. Without this an invalid command will generate one error message per task launched.
-
- 11 Mar, 2015 2 commits
-
-
Morris Jette authored
Cray - Fix for launching batch step within an existing job allocation. bug 1509
-
Morris Jette authored
Partially revert commit 8d91ae22 The bug was introduced in version 14.11.0-pre4. bug 1504
-
- 10 Mar, 2015 2 commits
-
-
Danny Auble authored
This is for bug 1514
-
Brian Christiansen authored
-
- 09 Mar, 2015 3 commits
-
-
Danny Auble authored
before.
-
David Bigagli authored
-
David Bigagli authored
-
- 06 Mar, 2015 1 commit
-
-
Brian Christiansen authored
Bug 1507
-
- 05 Mar, 2015 2 commits
-
-
Danny Auble authored
message comes in
-
David Bigagli authored
-
- 04 Mar, 2015 2 commits
-
-
Brian Christiansen authored
Bug 1501
-
Brian Christiansen authored
Bug 1501
-
- 03 Mar, 2015 5 commits
-
-
Danny Auble authored
cluster(s) requested.
-
David Bigagli authored
-
Brian Christiansen authored
Bug 1492
-
Morris Jette authored
For job running under a debugger, if the exec of the task fails, then cancel its I/O and abort immediately rather than waiting 60 seconds for I/O timeout.
-
Morris Jette authored
The option has not been functional or documented since Slurm version 2.0.
-
- 02 Mar, 2015 2 commits
-
-
David Bigagli authored
-
David Bigagli authored
-
- 27 Feb, 2015 5 commits
-
-
Morris Jette authored
This controls how long a requeued job must wait before it can restart, and 20 minutes is too long in most cases. Administrators can alter this configuration parameter if needed in case of slow Prolog or the like.
-
Morris Jette authored
Use this to specify the lifetime of a job step credential.
-
Brian Christiansen authored
Bug 1476
-
Morris Jette authored
Set the delay time for job requeue to the job credential lifetime (1200 second by default). This insures that prolog runs on every node when a job is requeued. (This change will slow down launch of re-queued jobs). Without this change, if a job is restated within 1200 seconds, the nodes previously used would not run the prolog again, since the job ID is still seen as active (from the previous execution). It is also advisable to set the value of DEFAULT_EXPIRATION_WINDOW in src/common/slurm_cred.c to the lowest value reasonable. We need to add a new configuration parameter so this is easly changed in the future.
-
Brian Christiansen authored
Display job's estimated NodeCount based off of partition's configured resources rather than the whole system's. Bug 1478
-