[GE users] Queue configuration question.

Reuti reuti at staff.uni-marburg.de
Tue Apr 11 06:53:58 BST 2006


Am 11.04.2006 um 01:18 schrieb Baudilio Tejerina:

> Hi Reuti,
>
> Can you please give an example of your alternative a) below?
>
>>
>> a) define one PE for each queue with similar names and request the  
>> PE with a wildcard
>
>
> If I understand you well, I should define a PE named   
> 'thnis_buckyball' like:
>
> pe_name       thnis_buckyball
> slots             999
> user_lists        NONE
> xuser_lists       NONE
> start_proc_args   NONE
> stop_proc_args    NONE
> allocation_rule   $pe_slots
> control_slaves    TRUE
> job_is_first_task FALSE
> urgency_slots     min
>
> and then use it in the parameter 'pe_list' on the queue of the same  
> name 'buckyball'.
>
> .... and repeat a similar procedure for all the queues.
>
>
> Then, submit a job with "qsub    -pe thnis_*    2      myjob"
>
> Is this what you mean in a)?

Yes, but in this case you would used a) and b) of my suggestions  
together, which is superfluous for your intended use I think. Just  
one PE with $pe_slots bound to one cluster queue containing all nodes  
dual nodes could do it already.

-- Reuti


> Thanks,
>
> Baudilio
>
>
>
> On Apr 10, 2006, at 2:12 PM, Reuti wrote:
>
>> Hi,
>>
>> Am 10.04.2006 um 19:08 schrieb Baudilio Tejerina:
>>
>>> Hi.
>>>
>>> In a clusters composed by single- and dual-processors machines, I  
>>> have defined queues associated with each individual computer so  
>>> that 'hostlist' contains just the name of machine (not a group)  
>>> and the 'slots' contains the number of CPUs that machine may  
>>> provide. For instance:
>>>
>>> qconf -sq buckyball
>>>
>>> qname                 buckyball
>>> hostlist                 buckyball
>>> seq_no                0
>>> ....
>>> slots                 1,[buckyball=2]
>>> ....
>>>
>>> Likewise, if the machine has a single CPU
>>>
>>> slots                 1,[zinc=1]
>>>
>>>
>>>
>>> It happens that if I submit a job requesting 2 CPUs, GE allocates  
>>> one from "buckyball" and the other from "zinc".
>>>
>>
>> this is the intended behavior. You can:
>>
>> a) define one PE for each queue with similar names and request the  
>> PE with a wildcard
>>
>> b) use allocation rule $pe_slots, this way you could still stay  
>> with one queue for all machines, as all slots have to be on one  
>> machine
>>
>>
>>>
>>> How can I have the job be allocated in a machine with two  
>>> processors and never in the way it is now?
>>> Related to this, I'd like to configure the queues so that if a  
>>> user requests more that 2 CPUs, the job gets always rejected.
>>>
>>
>> What is the definition of your PE now? Maybe you need a second PS  
>> with a different allocation rule.
>>
>> -- Reuti
>>
>>
>>>
>>> I've been reading  the documentation but I couldn't find  
>>> anything. In fact, I had thought that the configuration of 'one  
>>> queue for one node' would work, but apparently is not sufficient.
>>>
>>> Baudilio
>>>
>>> -------------------------------------------------------------------- 
>>> -
>>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
>>> For additional commands, e-mail: users-help at gridengine.sunsource.net
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
>> For additional commands, e-mail: users-help at gridengine.sunsource.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail: users-help at gridengine.sunsource.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list