- 20 Dec, 2018 1 commit
-
-
Brian Christiansen authored
Bug 6229
-
- 19 Dec, 2018 1 commit
-
-
Danny Auble authored
Bug 6239
-
- 18 Dec, 2018 5 commits
-
-
Dominik Bartkiewicz authored
Bug 5682 and 4584 Backport of ba07a6e09b6071
-
Dominik Bartkiewicz authored
other than knl. Bug 5603
-
Danny Auble authored
Bug 5603
-
Moe Jette authored
This patch also simplifies the code using bit_cnt instead of _bitstr_bits(). This isn't really necessary, but does look cleaner. Bug 6216
- 17 Dec, 2018 4 commits
-
-
Michael Hinton authored
Bug 6420
-
Danny Auble authored
Continuation of 2 commits ago. Bug 6159
-
Broderick Gardner authored
Continuation of last commit Bug 6159
-
Broderick Gardner authored
It was using the local cluster, sending the query to the wrong table Bug 6159
-
- 14 Dec, 2018 4 commits
-
-
Nate Rini authored
bug 6116
-
Nate Rini authored
bug 6116
-
Brian Christiansen authored
Bug 6237
-
Dominik Bartkiewicz authored
if OverTimeLimit is Unlimited. Bug 6093
-
- 13 Dec, 2018 1 commit
-
-
Danny Auble authored
-
- 11 Dec, 2018 3 commits
-
-
Tim Wickberg authored
-
Tim Wickberg authored
Update slurm.spec and slurm.spec-legacy as well.
-
Tim Wickberg authored
Bug 6029.
-
- 10 Dec, 2018 1 commit
-
-
Morris Jette authored
The cpu frequency set by the user is not exact with current kernels. There seems to be a fair variation depending upon timing and other events. This is resulting in test1.76 failing sporatically. This changes the logic to retry if the frequency differs by more than 10 percent rather than failing immediately.
-
- 08 Dec, 2018 1 commit
-
-
Marshall Garey authored
Bug 6029
-
- 07 Dec, 2018 2 commits
-
-
Nate Rini authored
Only print a warning for 18.08. If a user has SLURM_MEM_PER_CPU or SLURM_MEM_PER_NODE environment variables set for some reason this situation could be happening by accident, and we don't want to prevent the srun command from launching steps at this point. Bug 6058.
-
Broderick Gardner authored
Bug 5648.
-
- 06 Dec, 2018 8 commits
-
-
Janne Blomqvist authored
The Linux kernel default hard limit of 4096 for the number of file descriptors is quite small. Debian/Ubuntu have for a long time overridden this, increasing it to 1M. Recently systemd also bumped the default to 512k. https://github.com/systemd/systemd/blob/master/NEWS https://github.com/systemd/systemd/pull/10244 https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/ZN5TK3D6L7SE46KGXICUKLKPX2LQISVX/ https://github.com/systemd/systemd/commit/09dad04c49cae3ad2b319c9b4e7773fedd34309a Here the limits are increased as follows: - slurmd: 128k; some workloads like Hadoop/Spark need a lot of fd's, and recommend that the limit is increased to at least 64k. - slurmctld: 64k; per the Slurm high throughput and big system guides which recommend a file-max of at least 32k. - slurmdbd: 64k, matching slurmctld, though slurmdbd shouldn't need that many fd's, bumping the limit shouldn't hurt either. Bug 6171
-
Tim Wickberg authored
Bug 5248
-
Mike Nolta authored
Bug 6055
-
Mike Nolta authored
Add the following slurmctld return codes to the lua plugin: ESLURM_ACCESS_DENIED ESLURM_ACCOUNTING_POLICY ESLURM_INVALID_NODE_COUNT ESLURM_JOB_MISSING_SIZE_SPECIFICATION ESLURM_MISSING_TIME_LIMIT Bug 6055
-
Marshall Garey authored
Bug 5836.
-
Marshall Garey authored
-
Nate Rini authored
-
Nate Rini authored
Bug 6162
-
- 05 Dec, 2018 9 commits
-
-
Albert Gil authored
Bug 6163
-
Felip Moll authored
Backups already run it when dropping to backup. Bug 6098.
-
Marshall Garey authored
Remove the README and point to the web page. Add details on the disable_x11 option. Bug 5936.
-
Marshall Garey authored
Also throw an error message within stepd_available() if the nodename is not set or cannot be inferred correctly. Bug 5399.
-
Nate Rini authored
-
Brian Christiansen authored
-
Brian Christiansen authored
Spelling, suggestions, trailing whitespace.
-
Nate Rini authored
Bug 6044
-
Trey Dockendorf authored
Bug 6120
-