[GE users] Submitting jobs that should not run on the same hosts

hoffman michael.hoffman.2008 at gmail.com
Mon Feb 23 07:32:20 GMT 2009


templedf wrote:
> Unless there is a complex already configured that you can hijack,
> there's not much you can do.  What about requesting an amount of memory
> that guarantees that the jobs can't be co-scheduled (if memory is set to
> be consumable)?

I'd block other users' memory-consuming jobs if I did this though.

> If you go the host route, maybe instead of requesting
> specific hosts, you can request non-overlapping host groups (-l
> h=@hostgroup) or groups of hosts (-l 'h=host1|host2|host3').

That is a useful tip.

Thank you,
Michael

> hoffman wrote:
>> I am submitting several jobs that are fairly I/O intensive, so I do not want any of them running on the same host. Is there an easy way to ensure this?
>>
>> I do not have administrative access, so if the correct way requires setting up complex attributes or the like, I will just explicitly specify hostnames with qsub -l hostname=host001 rather than bug our sysadmins. (Which might be the easiest way to do it anyway.)
>>
>> Thanks,
>> Michael Hoffman
>>
>> ------------------------------------------------------
>> http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=112240
>>
>> To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].
>>
>
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=112328
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].
>



On 2/22/09, templedf <dan.templeton at sun.com> wrote:
> Unless there is a complex already configured that you can hijack,
> there's not much you can do.  What about requesting an amount of memory
> that guarantees that the jobs can't be co-scheduled (if memory is set to
> be consumable)?  If you go the host route, maybe instead of requesting
> specific hosts, you can request non-overlapping host groups (-l
> h=@hostgroup) or groups of hosts (-l 'h=host1|host2|host3').
>
> Daniel
>
> hoffman wrote:
>> I am submitting several jobs that are fairly I/O intensive, so I do not
>> want any of them running on the same host. Is there an easy way to ensure
>> this?
>>
>> I do not have administrative access, so if the correct way requires
>> setting up complex attributes or the like, I will just explicitly specify
>> hostnames with qsub -l hostname=host001 rather than bug our sysadmins.
>> (Which might be the easiest way to do it anyway.)
>>
>> Thanks,
>> Michael Hoffman
>>
>> ------------------------------------------------------
>> http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=112240
>>
>> To unsubscribe from this discussion, e-mail:
>> [users-unsubscribe at gridengine.sunsource.net].
>>
>
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=112328
>
> To unsubscribe from this discussion, e-mail:
> [users-unsubscribe at gridengine.sunsource.net].
>

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=112435

To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].



More information about the gridengine-users mailing list