On 02/23/2012 06:25 PM, S Joe wrote: > 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. >
A fundamental design philosophy of SGE is that you shouldn't have to request a specific queue when submitting a job. Instead, you request the resources your job needs, and let SGE determine the proper queue. Your approach in the second paragraph above is the more appropriate approach. When you submit a job that doesn't request the mascot resource, a job can still run on that queue, since that queue probably still meets all the other resource requirements. If you don't want those jobs running on mascot.q, you would have to specify mascot=false in your job submission. I think you can do this by setting the default value for mascot to false in your complex configuration, or force your users to specify the mascot resource when submitting a job. -- Prentice _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
