Am 12.12.2014 um 18:45 schrieb Greg Ball <[email protected]>: > > The target for the -hold_jid is a standard job and is assigned a priority. > The subsequent (second, third, etc,) jobs submitted with the -hold_jid option > receive no (0.00000) priority, I would like these jobs to receive their own > non-zero priorities but still be started sequentially.
They get no computed priority, as they are not eligible to start. Hence the computation of any priority can be skipped by the scheduler. They will get a computed priority once the job(s) specified in -hold_jid left the system automatically. -- Reuti > Regards, > > GM > > On Fri, Dec 12, 2014 at 12:26 PM, Reuti <[email protected]> wrote: > Hi, > > > Am 12.12.2014 um 15:22 schrieb Greg Ball <[email protected]>: > > > > When submitting jobs with dependency holds using the -hold_jid option the > > subordinate (held) jobs are assigned a 0 priority, as they inherit the > > priority of the hold target jobid. Is it possible for the held (hqw) jobs > > to each be assigned their own priority and still function sequentially, or > > are there alternate methods for processing sequential jobs such that they > > obtain their own priorities. > > I'm not quite clear what you want to achieve. You have three jobs - one > running and a second waiting for the end of that job. And then a third job > which is waiting for the completion of the second job. For this third job you > want an increased priority? > > --- Reuti > > > > Regards, > > > > GM > > _______________________________________________ > > users mailing list > > [email protected] > > https://gridengine.org/mailman/listinfo/users > > > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users > _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
