The suggestion sounds good but I'm not sure I understand step 1 - if it's
going to be assigned by project and not user - can I still have "powerful"
users in my normal default project that have more tickets there?
I should really read about projects. thanks for the lead.

On Wed, Feb 8, 2017 at 1:25 PM, William Hay <w....@ucl.ac.uk> wrote:

> On Wed, Jan 18, 2017 at 05:17:15PM +0200, Ben Daniel Pere wrote:
> >    Hi guys,
> >    Is there a way to make a certain queue (or maybe even certain jobs
> upon
> >    submission) not count for the tickets a user is running?
> >    We recently started having a very "cheap" tasks that basically wait
> for
> >    external resources to be ready (could take hours) and then launches a
> >    normal task array and end. so we put these cheap ones in their own
> queue
> >    (cheap.q) which we made "free" (we excluded it from any resource quota
> >    rules we have) because it takes virtually no resources - but now users
> >    which have say 100 tasks running on this queue doing nothing can run
> 100
> >    less tasks in the important queues and when the cluster is full these
> guys
> >    are rightfully complaining this is unfair..
> >    So is there a way to make the cheap.q tasks not count for tickets?
> either
> >    a queue setting or a job setting upon submission (the jobs are being
> sent
> >    through a wrapper we made, no user really calls qsub directly)
> >    Thank you!
> >     - Ben
> If you aren't already using projects you could try the following:
> 1)Assign tickets based on projects rather than users.
> 2)Give each user their own default project and associate their tickets
> with that.
> 3)Add a cheap project that is prohibited from regular queues and the only
> project allowed
> in the cheap.q.
> 4)All users are members of their default project and the cheap project
>
> When users want to use the cheap queue they request the cheap project.
>
> A little more work setting up new users but should be scriptable.
>
> If you are using project then it might be possible to modify this scheme
> and still have it work but that depends on how you are using
> projects.
>
> William
>
_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users

Reply via email to