Garrick Staples garrick at usc.edu
Wed Nov 11 09:41:05 MST 2009

On Wed, Nov 11, 2009 at 03:29:29PM +0100, Lech Nieroda alleged:
> Dear users and developers,
> we have a heterogeneous cluster where nodes have 16GB and 64GB RAM,
> our maui version is 3.2.6p21.
> Although the NODEALLOCATIONPOLICY MINRESOURCE is set, jobs are
> sometimes assigned to the larger nodes even though their resources
> could be satisfied by a smaller node.
> I've taken a quick look into the source code and it seems like growing
> blocks of memory sizes are compared to corresponding node resources
> and after some additional checks the right nodes are selected. The
> block sizes vary between 64 and 8192 (probably MB), see
> src/moab/MSched.c, lines 1180+
> Which is probably the reason why nodes with more than 8GB free memory
> are perceived as equal by the MINRESOURCE checking routine...
> Is this going to be fixed? Is there another approach that might work?

With NODEALLOCATIONPOLICY LASTAVAILABLE, Maui assigns nodes from the bottom up in torque's node list.

So then just sort the nodes however you want in torque.

Garrick Staples, GNU/Linux HPCC SysAdmin
University of Southern California

Life is Good!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/mauiusers/attachments/20091111/2be3d36c/attachment.bin 

More information about the mauiusers mailing list