Am 24.02.2012 um 15:36 schrieb Prentice Bisbal: > On 02/23/2012 07:05 PM, Reuti wrote: >> Hi, >> >> Am 24.02.2012 um 00:25 schrieb S Joe: >> >>> 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. >> Yeah, requesting a resource is more SGE style than requesting a dedicated >> queue. >> >> How did you set up the complex? It sounds like it's not set to "requestable >> FORCED" but "requestable yes" only. > > Does it really need to be forced? Can't you just set the default to
No. If you don't specify it on the command line, then it means: I don't care whether it has this feature or not. > value to false in the complex configuration? Default values are only for consumables. -- Reuti >> NB: if you attach the complex to the exechosts and not the queue, it might >> even work to have only one queue in the cluster. > > I agree. I try to keep my number of queues to a minimum. > > Prentice > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
