[GE users] automatic suspension on full cluster

reuti reuti at staff.uni-marburg.de
Wed Feb 10 18:08:37 GMT 2010


    [ The following text is in the "utf-8" character set. ]
    [ Your display is set for the "ISO-8859-10" character set.  ]
    [ Some characters may be displayed incorrectly. ]

Am 10.02.2010 um 18:48 schrieb fjmodrego:

> This reminds me a lot to the mourned queuing system used by DEC in
> their VMS. I have not found anything similar. I miss its handling of
> priorities and cpu resource assignement to users.

Although unrelated:  I miss FILES-11 ability of having version  
numbers for files.

-- Reuti


> I wonder whether anybody can hint to a similar system nowadays...
> It would be very helpful
>
>
> 	F.J. Modrego
>
>
> El 10/02/2010, a las 15:00, massot escribió:
>
>> Hello,
>>
>> I'm trying to deal with the issue of full cluster (no available
>> slot). I
>> have a cluster to which all users have equal access. The problem is
>> that
>> when there's no remaining slot, some users have to wait until the
>> end of
>> jobs of other users, who sometimes run a lot of jobs. It's unfair. On
>> the other hand using individual job quotas is often a waste of
>> resources
>> since you can have a cluster that is not full.
>>
>> Here is the ideal configuration for my cluster. Anyone can submit as
>> many jobs as he wants if the cluster is not full. If the cluster is
>> full
>> and someone wants to submit a job, instead of having this job  
>> pending,
>> the person who runs the biggest number of jobs gets one of his jobs
>> suspended, and a slot is freed so the job of the first person can  
>> run.
>> As soon as slots are available again, jobs suspended because of full
>> cluster are resumed.
>> I could build a system based on cron jobs suspending and resuming
>> jobs,
>> and adjusting the "slots" queue attributes on the fly, but that  
>> sounds
>> like a quite ugly solution.
>> Can you think of an elegant way to configure my ideal cluster?
>> -- 
>> Bernard Massot
>>
>> ------------------------------------------------------
>> http://gridengine.sunsource.net/ds/viewMessage.do? 
>> dsForumId=38&dsMessageId=244250
>>
>> To unsubscribe from this discussion, e-mail: [users- 
>> unsubscribe at gridengine.sunsource.net
>> ].
>
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do? 
> dsForumId=38&dsMessageId=244278
>
> To unsubscribe from this discussion, e-mail: [users- 
> unsubscribe at gridengine.sunsource.net].
>

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

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



More information about the gridengine-users mailing list