Hi,
I observered that as well: maui will not place a reservation on a
node in offline/down state, and if the node comes back online, maui
has to be restarted for the reservation to take effect. In this way,
jobs could start on nodes where they shouldn't.
If this is a serious problem, I would define a property on the
complementary set of nodes and specify this property as
resources_default.neednodes for all other queues (or maybe as
default for all queues in the server section). This should be more robust
w.r.t offline/down states, as the node properties don't care about
node states.
If there is a way to make the maui reservations react instantly to
changes in node state, I would like to know.
Regards,
Burkhard Bunk.
----------------------------------------------------------------------
b...@physik.hu-berlin.de Physics Institute, Humboldt University
fax: ++49-30 2093 7628 Newtonstr. 15
phone: ++49-30 2093 7980 12489 Berlin, Germany
----------------------------------------------------------------------
On Fri, 23 Aug 2013, Pankaj Dorlikar wrote:
On Thu, Aug 22, 2013 at 10:06 PM, Pankaj Dorlikar
<pankaj.dorli...@gmail.com> wrote:
Hi,
The solution provided worked for us. But one issue is, if one of the
nodes from hostlist defined in
SRCFG[res1] HOSTLIST goes down or is not online and if the maui is
restarted or when maui updates the reservations and node is not
available, the reservation (res1) is not set and then specifying the
queue as evalq wont work. Also, the jobs where evalq is not specified
also lands on the these nodes which we dont want ot happen. How we
can prevent such jobs from landing on these nodes?
thanks.
On Thu, Jul 11, 2013 at 9:54 PM, Pankaj Dorlikar
<pankaj.dorli...@gmail.com> wrote:
option 2 worked!!! Once again thank you for your kind
help....
thanks..
On Thu, Jul 11, 2013 at 10:05 AM, Pankaj Dorlikar
<pankaj.dorli...@gmail.com> wrote:
thanks a lot. i will try and inform you.
On Wed, Jul 10, 2013 at 10:46 PM, Burkhard Bunk
<b...@physik.hu-berlin.de> wrote:
Hi,
if you assign a property to specific nodes
and also specify it with
resources_default.neednodes of the respective
queue(s) will direct
the queue(s) to the special nodes.
This will not prevent other queues to address
the special nodes as well.
There are two ways to achieve this, AFAIK:
(1) Define another property on all other
nodes and give it to
resources_default.neednodes for all other
queues.
(2) Use maui to reserve the special nodes for
the respective queues.
You may have to include stanzas like the
following in maui.cfg:
SRCFG[res1]
HOSTLIST=node1$,node10$,node11$,node20$
SRCFG[res1] PERIOD=INFINITY
SRCFG[res1] CLASSLIST=evalq
"res1" names the reservation (dummy) and
groups the statements together.
Nodenames are terminated with "$" to prevent
hostname expansion.
You may use patterns like node1[0-9] as well
but...
check reservations with
showres # summary only
showres -n # list by nodes
checknode <nodename>
Hope that helps.
Regards,
Burkhard Bunk.
----------------------------------------------------------------------
b...@physik.hu-berlin.de Physics
Institute, Humboldt University
fax: ++49-30 2093 7628 Newtonstr. 15
phone: ++49-30 2093 7980 12489 Berlin,
Germany
----------------------------------------------------------------------
On Wed, 10 Jul 2013, Pankaj Dorlikar wrote:
Hi,
We have torque 2.5.8 and maui
3.2.6p1. We have a set of 4 nodes
where we have
assigned property to those nodes
as EVAL (server_priv/nodes) and
created a
seperate execution queue (evalq)
for these 4 nodes. We have given
resources_default.neednodes
parameter in qmgr while creation
of this queue We
want to achieve that user
specifying the queue as evalq and
specifying
property as EVAL should only land
on these 4 nodes . No other jobs
should go
on these nodes. How to do it?
--
Pankaj V. Dorlikar
--
Pankaj V. Dorlikar
--
Pankaj V. Dorlikar
--
Pankaj V. Dorlikar
--
Pankaj V. Dorlikar
_______________________________________________
mauiusers mailing list
mauiusers@supercluster.org
http://www.supercluster.org/mailman/listinfo/mauiusers
