Skip to content
Snippets Groups Projects
Commit 875153e4 authored by Moe Jette's avatar Moe Jette
Browse files

Update select/cons_res web page (Susanne Balle, HP, cons_res_doc_patch_3_29_06).

parent 86406afa
No related branches found
No related tags found
No related merge requests found
...@@ -22,6 +22,7 @@ documents those changes that are of interest to users and admins. ...@@ -22,6 +22,7 @@ documents those changes that are of interest to users and admins.
WARNING: "JobAcctType=jobacct/log" is no longer supported. WARNING: "JobAcctType=jobacct/log" is no longer supported.
-- Removed vestigal 'bg' names from bluegene plugin and smap -- Removed vestigal 'bg' names from bluegene plugin and smap
-- InactiveLimit parameter is not enforced for RootOnly partitions. -- InactiveLimit parameter is not enforced for RootOnly partitions.
-- Update select/cons_res web page (Susanne Balle, HP, cons_res_doc_patch_3_29_06).
* Changes in SLURM 1.1.0-pre2 * Changes in SLURM 1.1.0-pre2
============================= =============================
......
...@@ -35,6 +35,16 @@ this plug-in is described below. ...@@ -35,6 +35,16 @@ this plug-in is described below.
view, working the same way as when using the default node selection scheme.</li> view, working the same way as when using the default node selection scheme.</li>
<li>We introduce a new switch <i>--exclusive</i> which will allow users to reserve/use nodes in <li>We introduce a new switch <i>--exclusive</i> which will allow users to reserve/use nodes in
exclusive mode even when consumable resources is enabled. see "man srun" for details. </li> exclusive mode even when consumable resources is enabled. see "man srun" for details. </li>
<li>Using the <i>--overcommit</i> or <i>-O</i> switch in the
<b>select/cons_res</b> environment is only allowed/possible when a user
requests dedicated nodes using the <i>--exclusive</i>
switch. Overcommiting CPUs in a non-dedicated environment would
impact jobs that are co-located on the nodes which is not a
desirable feature.We are currently looking into "pinning" the
processes to jobs' allocated CPUs which should allow users in
<b>the future</b> to overcommit CPUs in a the <b>select/cons_res</b> environment
without affecting co-located jobs.</li>
<li>SLURM's default <b>select/linear</b> plugin is using a best fit algorithm based on <li>SLURM's default <b>select/linear</b> plugin is using a best fit algorithm based on
number of consecutive nodes. We have chosen the same node allocation number of consecutive nodes. We have chosen the same node allocation
approach for consistency.</li> approach for consistency.</li>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment