[torquedev] [Bug 93] Resource management semantics of Torque need to be well defined

bugzilla-daemon at supercluster.org bugzilla-daemon at supercluster.org
Mon Dec 6 14:32:19 MST 2010


http://www.clusterresources.com/bugzilla/show_bug.cgi?id=93

--- Comment #17 from Ken Nielson <knielson at adaptivecomputing.com> 2010-12-06 14:32:19 MST ---
(In reply to comment #16)
> (In reply to comment #12)
> > 
> > Also in section 2.1.2 under nodes and ppn:
> > http://www.clusterresources.com/products/torque/docs/2.1jobsubmission.shtml
> 
> Hopefully this:
> 
> "By default, the node resource is mapped to a virtual node (that is, directly
> to a processor, not a full physical compute node). "
> 
> is not true.  Hopefully, this is more true (its how our scheduler works at
> least):
> 
> "By default, the node resource is mapped to a virtual node (that is, multiple
> virtual nodes (from one or more jobs) may be allocated to the same physical
> node (host) provided that all other resource requests can be satisfied by the
> shared physical host). "

I started to add your corrections to the documentation when I realized we have
another item we need to define. That is the host. In context of nodes as a
resource a node is not the same as a host. When we are configuring the nodes
file we are actually configuring execution hosts. When we are requesting nodes
we are requesting parts of each host.

Please add any comments you think are appropriate.

-- 
Configure bugmail: http://www.clusterresources.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the torquedev mailing list