- 15 Jul, 2015 3 commits
-
-
Morris Jette authored
-
Nathan Yee authored
-
Nathan Yee authored
Bug 1798
-
- 14 Jul, 2015 3 commits
-
-
Danny Auble authored
-
Morris Jette authored
Previous logic could fail to update some tasks of a job array for some fields. bug 1777
-
Danny Auble authored
bind to the interface of return of gethostname instead of any address on the node which avoid RSIP issues in Cray systems. This is most likely useful in other systems as well.
-
- 13 Jul, 2015 2 commits
-
-
Morris Jette authored
Fix to job array update logic that can result in a task ID of 4294967294. To reproduce: $ sbatch --exclusive -a 1,3,5 tmp Submitted batch job 11825 $ scontrol update jobid=11825_[3,4,5] timelimit=3 $ squeue JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON) 11825_3 debug tmp jette PD 0:00 1 (None) 11825_4 debug tmp jette PD 0:00 1 (None) 11825_5 debug tmp jette PD 0:00 1 (None) 11825 debug tmp jette PD 0:00 1 (Resources) A new job array entry was created for task ID 4 and the "master" job array record now has a task ID of 4294967294. The logic with the bug was using the wrong variable in a test. bug 1790
-
Gene Soudlenkov authored
Bug 1799
-
- 11 Jul, 2015 1 commit
-
-
Nathan Yee authored
Increase total backfill scheduler run time in stats_info_response_msg data structure from 32 to 64 bits in order to prevent overflow.
-
- 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
Modify slurmctld outgoing RPC logic to support more parallel tasks (up to 85 RPCs and 256 pthreads; the old logic supported up to 21 RPCs and 256 threads). This change can dramatically improve performance for RPCs operating on small node counts. bug 1786
-
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
-
Danny Auble authored
-
- 09 Jul, 2015 2 commits
-
-
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
-
Morris Jette authored
Changed spaces to tabs at start of lines. Minor changes to some formatting. Added the new files to the RPM (slurm.spec file). Prevent memory leak of "l_name" variable if which_power_layout() function is called more than once. Initialize "cpufreq" variable in powercap_get_cpufreq() function. Array "tmp_max_watts_dvfs" could be NULL and used if "max_watts_dvfs" variable is NULL in powercap_get_node_bitmap_maxwatts_dvfs() Variable "tmp_pcap_cpu_freq" could be used with uninitialized value in function _get_req_features() Variable "tmp_max_watts" could be used with uninitialized value in function _get_req_features() Array "tmp_max_watts_dvfs" could be used with uninitialized value in function _get_req_features() Array "allowed_freqs" could be NULL and used if "node_record_count" variable is zero in powercap_get_job_nodes_numfreq() Overwriting a memory buffer header (especially with different data types) is just asking for something bad to happen. This code from function powercap_get_job_nodes_numfreq(): allowed_freqs = xmalloc(sizeof(int)*((int)num_freq+2)); allowed_freqs[-1] = (int) num_freq; Clean up memory on slurmctld shutdown
-
- 08 Jul, 2015 3 commits
-
-
David Bigagli authored
-
Morris Jette authored
-
Morris Jette authored
-
- 07 Jul, 2015 6 commits
-
-
Trey Dockendorf authored
-
Trey Dockendorf authored
Add job record qos field and partition record allow_qos field.
-
Trey Dockendorf 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>
-
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 2 commits
-
-
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
-
- 02 Jul, 2015 2 commits
-
-
Morris Jette authored
Original patch from LLNL assumed Munge was installed, which would result in a build error if the Munge development package was not installed
-
Morris Jette authored
Add association usage information to "scontrol show cache" command output.
-
- 01 Jul, 2015 2 commits
-
-
Brian Christiansen authored
When submitting a job with srun -n# the job may be allocated more than # because the job was given the whole core or socket (eg. CR_CORE, CR_SOCKET). sacct showed only what the step used and not the allocation. This commit shows the job and the step if job and step cpus are different.
-
Morris Jette authored
Major re-write of the sreport command to support --tres job option and permit users to select specific tracable resources to generate reports for. For most reports, each TRES is listed on a separate line of output with its name. The default TRES type is "cpu" to minimize changes to output.
-
- 30 Jun, 2015 2 commits
-
-
Thomas Cadeau authored
Bug 1745
-
Brian Christiansen authored
This reverts commit 3f91f4b2.
-
- 29 Jun, 2015 2 commits
-
-
Nathan Yee authored
Bug 1745
-
David Bigagli authored
-
- 26 Jun, 2015 2 commits
-
-
Danny Auble authored
-
Brian Christiansen authored
Bug 1746
-
- 25 Jun, 2015 2 commits
-
-
Morris Jette authored
-
Morris Jette authored
-
- 24 Jun, 2015 2 commits
-
-
David Bigagli authored
-
Morris Jette authored
-