-
Notifications
You must be signed in to change notification settings - Fork 1
/
5.4nodeavailability.html
69 lines (51 loc) · 4.08 KB
/
5.4nodeavailability.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy for Linux (vers 25 March 2009), see www.w3.org">
<title></title>
</head>
<body>
<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.html"><img src="home.png" title="Home" alt="Home" border="0"></a> <a href="5.0prioritization.html"><img src="upArrow.png" title="Up" alt="Up" border="0"></a> <a href="5.3nodeaccess.html"><img src="prevArrow.png" title="Previous" alt="Previous" border="0"></a> <a href="5.5taskdistribution.html"><img src="nextArrow.png" title="Next" alt="Next" border="0"></a>
</div>
<h1>5.4 Node Availability Policies</h1>
<p>Schedulers will allow jobs to be launched on a given compute node as long as the node is not full or <i>busy</i>. The parameter <b><a href="a.fparameters.html#nodeavailabilitypolicy">NODEAVAILABILITYPOLICY</a></b> allows a site to determine what criteria constitutes a node being busy . The legal settings are listed in the table below:</p>
<table cellpadding="2" cellspacing="2" border="1" width="100%">
<tbody>
<tr>
<td valign="top"><b>Availability Policy</b><br></td>
<td valign="top"><b>Description</b><br></td>
</tr>
<tr>
<td valign="top"><b>DEDICATED</b><br></td>
<td valign="top">The node is considered busy if dedicated resources equal or exceed configured resources<br></td>
</tr>
<tr>
<td valign="top"><b>UTILIZED</b><br></td>
<td valign="top">The node is considered busy if utilized resources equal or exceed configured resources<br></td>
</tr>
<tr>
<td valign="top"><b>COMBINED</b><br></td>
<td valign="top">The node is considered busy if either dedicated or utilized resources equal or exceed configured resources<br></td>
</tr>
</tbody>
</table>
<p>The default setting for all nodes is <b>COMBINED</b> indicating that a node can accept workload so long as the jobs which the node was allocated to do not request or utilize more resources than the node has available. In a load balancing environment, this may not be the desired behavior. Setting the <b>NODEAVAILABILITYPOLICY</b> parameter to <b>UTILIZED</b> will allow jobs to be packed onto a node even if the aggregate resources requested exceeds the resources configured. For example, assume a scenario with a 4 processor compute node and 8 jobs requesting 1 processor each. If the resource availability policy was set to <b>COMBINED</b> , this node would only allow 4 jobs to start on this node even if the jobs induced a load of less than 1.0 each. With the resource availability policy set to <b>UTILIZED</b>, the scheduler would continue to allow jobs to be started on the node until the node's load average exceeded a per processor load value of 1.0 (in this case, a total load of 4.0). To prevent a node from being over populated within a single scheduling iteration, Maui will artificially raise the node's load for one scheduling iteration when starting a new job. On subsequent iterations, the actual measured node load information will be used.</p>
<div class="navIcons bottomIcons">
<a href="index.html"><img src="home.png" title="Home" alt="Home" border="0"></a> <a href="5.0prioritization.html"><img src="upArrow.png" title="Up" alt="Up" border="0"></a> <a href="5.3nodeaccess.html"><img src="prevArrow.png" title="Previous" alt="Previous" border="0"></a> <a href="5.5taskdistribution.html"><img src="nextArrow.png" title="Next" alt="Next" border="0"></a>
</div>
</div>
</div>
</div>
<div class="sub-content-btm"></div>
</div>
</body>
</html>