- 13 Jul, 2015 1 commit
-
-
Gene Soudlenkov authored
Bug 1799
-
- 10 Jul, 2015 4 commits
-
-
Morris Jette authored
remove new capabilities added in comit ad9c2413 Leave the new logic only in version 15.08, which has related performance improvements in the slurmctld agent code, see commit 53534f49
-
Morris Jette authored
Correct "sdiag" backfill cycle time calculation if it yields locks. A microsecond value was being treated as a second value resulting in an overflow in the calcuation. bug 1788
-
Morris Jette authored
-
Morris Jette authored
-
- 09 Jul, 2015 1 commit
-
-
Morris Jette authored
The slurmctld logic throttles some RPCs so that only one of them can execute at a time in order to reduce contention for the job, partition and node locks (only one of the effected RPCs can execute at any time anyway and this lets other RPC types run). While an RPC is stuck in the throttle function, do not count that thread against the slurmctld thread limit. but 1794
-
- 08 Jul, 2015 7 commits
-
-
Morris Jette authored
-
Danny Auble authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
- 07 Jul, 2015 6 commits
-
-
Danny Auble authored
-
Trey Dockendorf authored
This patch moves the QOS update of an existing job to be before the partition update. This ensures a new QOS value is the value used when doing validations against things like a partition's AllowQOS and DenyQOS. Currently if a two partitions have AllowQOS that do not share any QOS, the order of updates prevents a job from being moved from one partition to another using something like the following: scontrol update job=<jobID> partition=<new part> qos=<new qos>
-
Danny Auble authored
-
Danny Auble authored
-
David Bigagli authored
-
Morris Jette authored
Correct task layout with CR_Pack_Node option and more than 1 CPU per task. Previous logic would place one task per CPU launch too few tasks. bug 1781
-
- 06 Jul, 2015 4 commits
-
-
Nathan Yee authored
-
Nathan Yee authored
-
Morris Jette authored
Backfill scheduler now considers OverTimeLimit and KillWait configuration parameters to estimate when running jobs will exit. Initially the job's end time is estimated based upon it's time limit. After the time limit is reached, the end time estimate is based upon the OverTimeLimit and KillWait configuration parameters. bug 1774
-
Morris Jette authored
Backfill scheduler: The configured backfill_interval value (default 30 seconds) is now interpretted as a maximum run time for the backfill scheduler. Once reached, the scheduler will build a new job queue and start over, even if not all jobs have been tested. bub 1774
-
- 03 Jul, 2015 1 commit
-
-
Morris Jette authored
-
- 30 Jun, 2015 3 commits
-
-
Thomas Cadeau authored
Bug 1745
-
Brian Christiansen authored
This reverts commit 3f91f4b2.
-
Danny Auble authored
and test21.* updated to use them.
-
- 29 Jun, 2015 1 commit
-
-
Nathan Yee authored
Bug 1745
-
- 25 Jun, 2015 3 commits
-
-
David Bigagli authored
-
Danny Auble authored
ESLURM_DB_CONNECTION when in error.
-
Morris Jette authored
-
- 24 Jun, 2015 2 commits
-
-
Morris Jette authored
-
David Bigagli authored
-
- 23 Jun, 2015 2 commits
-
-
David Bigagli authored
-
Morris Jette authored
-
- 22 Jun, 2015 5 commits
-
-
Morris Jette authored
Updates of existing bluegene advanced reservations did not work at all. Some multi-core configurations resulting in an abort due to creating core_bitmaps for the reservation that only had one bit per node rather than one bit per core. These bugs were introduced in commit 5f258072
-
Morris Jette authored
-
Morris Jette authored
-
David Bigagli authored
-
Thomas Cadeau authored
-