Hi, Am 22.09.2014 um 16:01 schrieb Paul Jewell [Rudraya]:
> I am trying to fix a situation in which many long running jobs are being ran > on the grid and another job which is a higher priority needs to be ran > immediately. The issue I am running into is the operation of the "suspend" > function in the gridengine "qmod" command. It seems that by suspending a job > with -sj <job> the job will change to a "s" stats, but will continue to sit > on the queue for the node This is the intended behavior. Resources are still allocated to the suspended jobs (cores, memory). You will need another queue and in the essence oversubscribe the machine when adding up all used slots of a maschine (i.e. normal.q + urgent.q). This can also be automated by using "subordinate_list" in the queue definition. -- Reuti > instead of letting other jobs that are waiting to start begin. Is this the > intended behavior? How can I suspend jobs to allow other jobs to run in their > place, or is it required to delete them completely? > > Thank you and have an awesome day, > -Paul > _______________________________________________ > users mailing list > users@gridengine.org > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
