<br><br><div class="gmail_quote">On Tue, Mar 30, 2010 at 9:55 AM, Charles Johnson <span dir="ltr"><<a href="mailto:charles.johnson@accre.vanderbilt.edu">charles.johnson@accre.vanderbilt.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
About the nodes file ... I have always been under the impression that<br>
the nodes file gives an ordering to nodes selected for jobs, i.e.,<br>
nodes at the top of the list are considered before nodes at the<br>
bottom. We are currently in a down time for refreshing hardware, and<br>
the whole cluster is quiescent. As a test of hardware we submitted a<br>
single job suitable for any one of several hundred nodes at the top of<br>
the nodes file. The job ran on a node roughly halfway down the nodes<br>
file. Again, there were no other jobs on the cluster.<br>
<br>
I am curious as to why? Any ideas?<br>
<br>
We are using torque 2.4.5 and moab 5.3.6<br></blockquote></div><br><br>This is really a Moab question since Moab selects the node that the job will run on, it has nothing to do with the order of the nodes in the TORQUE node file. I think the default for Moab might be "last fit", so as it scans the available nodes it will select the last one it finds that satisfies the requirements for the job. There is a "first fit" and "best fit" option if I remember correctly.<br>
<br>With the fifo scheduler, then yes, I think the job would run on the first available node in the node list. <br>