Hi,

Most jobs in our cluster we restrict to a certain subset of nodes in our 
cluster.  I have one job type that can run on any node.  So I setup a specific 
queue for that type of job and assign it all nodes and ask users to submit 
those jobs to that queue (-q mascot.q).  The rest of the queues in our 
configuration are limited to the subset of nodes.  Unfortunately when users 
submit jobs and don't request a queue (as they normally would) sometimes they 
end up in the mascot.q when all other queues are full.


So to addrss the problem I tried creating an requestable boolean complex called 
mascot and setting it as a complex on the mascot queue.  The idea was that 
instead of requesting the mascot.q you'd request the mascot resource and those 
job types would be assigned to the mascot.q and run on any node in the 
cluster.  Any other jobs would never get put in the mascot.q as they don't have 
that resource.  For some reason this doesn't work -- when jobs are submitted 
without the mascot resource they still end up in the mascot queue.

I'm sure I'm either not understanding something or doing something simple wrong.

Thanks,
Joe
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users

Reply via email to