<div class="sright"> <div class="sub-content-head"> Maui Scheduler </div> <div id="sub-content-rpt" class="sub-content-rpt" > <div class="tab-container docs" id="tab-container"> <div class="topNav"> <div class="docsSearch"> </div> <div class="navIcons topIcons"> <a href="index.php"><img src="/resources/docs/images/home.png" title="Home" alt="Home" border="0"></a> <a href="12.0generalnodeadmin.php"><img src="/resources/docs/images/upArrow.png" title="Up" alt="Up" border="0"></a> <a href="12.2nodeattributes.php"><img src="/resources/docs/images/prevArrow.png" title="Previous" alt="Previous" border="0"></a> <a href="12.4consumablegres.php"><img src="/resources/docs/images/nextArrow.png" title="Next" alt="Next" border="0"></a> </div> <h1>12.3 Node Specific Policies</h1> Specification of node policies is fairly limited within Maui mainly because the demand for such policies is limited. These policies allow a site to specify on a node by node basis what the node will and will not support. Node policies may be applied to specific nodes or applied system wide using the specification '<tt>NODECFG[DEFAULT] ...</tt>' Note that these policies were introduced over time so not all policies are supported in all versions. <p><b>MAXJOB</b> <p> This policy constrains the number of total independent jobs a given node may run simultaneously. It can only be specified via the <b>NODECFG</b> parameter. <p><b>MAXJOBPERUSER</b> <p><b></b> This policy constrains the number of total independent jobs a given node may run simultaneously associated with any single user. Like <b>MAXJOB</b>, it can only be specified via the <a href="a.fparameters.php#nodecfg">NODECFG</a> parameter. <p><b>MAXLOAD</b> <p> <b>MAXLOAD</b> constrains the CPU load the node will support as opposed to the number of jobs. If the node's load exceeds the <b>MAXLOAD</b> limit and the <a href="a.fparameters.php#nodeloadpolicy">NODELOADPOLICY</a> parameter is set to <b>ADJUSTSTATE</b> , the node will be marked busy. Under Maui 3.0, the max load policy could be applied system wide using the parameter <a href="a.fparameters.php#nodemaxload">NODEMAXLOAD</a>. <p><img SRC="/images/note.gif" height=24 width=20> Node policies are used strictly as constraints. If a node is defined as having a single processor or the <a href="a.fparameters.php#nodeaccesspolicy">NODEACCESSPOLICY</a> is set to <b>DEDICATED</b>, and a <b>MAXJOB</b> policy of 3 is specified, Maui will probably not run more than one job per node. A node's configured processors must be specified so that multiple jobs may run and then the <b>MAXJOB</b> policy will be effective. The number of configured processors per node is specified on a resource manager specific basis. PBS, for example, allows this to be adjusted by setting the number of virtual processors, 'np' per node in the PBS 'nodes' file. <p><b>Example:</b> <p>--- <br><tt># maui.cfg</tt><tt></tt> <p><tt>NODECFG[node024] MAXJOB=4 MAXJOBPERUSER=2</tt> <br><tt>NODECFG[node025] MAXJOB=2</tt> <br><tt>NODECFG[node026] MAXJOBPERUSER=1</tt> <br><tt>NODECFG[DEFAULT] MAXLOAD=2.5</tt> <br>... <br>--- <div class="navIcons bottomIcons"> <a href="index.php"><img src="/resources/docs/images/home.png" title="Home" alt="Home" border="0"></a> <a href="12.0generalnodeadmin.php"><img src="/resources/docs/images/upArrow.png" title="Up" alt="Up" border="0"></a> <a href="12.2nodeattributes.php"><img src="/resources/docs/images/prevArrow.png" title="Previous" alt="Previous" border="0"></a> <a href="12.4consumablegres.php"><img src="/resources/docs/images/nextArrow.png" title="Next" alt="Next" border="0"></a> </div> </div> </div> </div> <div class="sub-content-btm"></div> </div> </div>