[torqueusers] Reservation problem with recent torque

Dave Jackson jacksond at clusterresources.com
Fri Jun 16 09:09:20 MDT 2006


  If you are using Moab/Maui, this is controlled by the scheduler
JOBNODEMATCHPOLICY parameter, and not by TORQUE.  If this parameter is
set to EXACTNODE, you will get 3 nodes with 1 processor each.  If it is
not set, it is up to the scheduler's discression regarding task
placement.  I think it is unlikely that any of the recent TORQUE
enhancements would cause this.


On Fri, 2006-06-16 at 16:44 +0200, Martin Schafföner wrote:
> Hi,
> there is yet another thing which bothering me about 2.1.x: If I submit a job 
> with "-l nodes=3:ppn=1" I used to get 1 processor on 3 nodes each (they are 
> SMP-HT ones, see my other post). Now I get 3 processors on one node, which is 
> not quite what I had intended. Have I missed another behind-the-scenes 
> change?
> Regards,

More information about the torqueusers mailing list