Hi, > Am 18.01.2017 um 16:17 schrieb Ben Daniel Pere <ben.p...@gmail.com>: > > 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
Running or waiting? Above you wrote, that these cheap job are some kind of submitter, which submits the real array job in a short time (a couple and seconds?) and end? > 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) You could create a second cell in SGE. This instance is independent from the real queues and share just the binaries, i.e. you need a second qmaster for this cell. Inside the jobscript, you can change the $SGE_CELL and address the different instance. Note that (depending on your set up) you need different ports for this one (qmaster and execd) and also set them in the cheap submission job to the correct values. In case the queue and qmaster for the "cheap" tasks is on a dedicated machine, this could be avoided. -- Reuti
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
