The expected behavior would be that when there is never an host with 12 slots free, that your cluster will be filled up with 4 slot jobs, even when they have lower priorities. The reservation you gave the 12 slot jobs will be attached at the end of that year. Hence I would assume that your 12 slot job will finally run in one year (under the assumption that you have always running 4 slots jobs on all of your host). You could try to submit without duration (s_rt) and set the default duration to the expected runtime. Then I would assume that that the first 12slots job will begin reservation after the "default_duration" periode (meaning that it begins to keep slots free, or to backfill shorter jobs if there are any.) Don't forget -R y like you did before.
My 2 cents, Daniel Am 25.05.2012 um 11:10 schrieb Richard Ems: > Hi list, > > I searched through the mailing list and tried using google, but couldn't > found an answer to my question. > > The (simplified) situation: > > We have a group of nodes with 12 slots. > We submit there parallel jobs requesting 4 or 12 slots. > We defined 2 PEs allocating 4 or 12 slots and associated to that group > of nodes in one queue. > Max_reservation is set to 20 (now increased to 50, what are the > implications of this?). > s_rt is set to 31536000 (which is one year time in seconds). > default_duration was set to 8760 (one year also, changed now to 9999) > > What we see now is that, despite setting a higher priority and asking > for reservation with "-R y" when submitting jobs to the 12 slots PE, > jobs previously submitted with lower priority and no reservation and > asking for the 4 slots PE get started before the previous one. > > Is this expected behavior or are we doing a configuration error? Or is > it a bug? Or a feature? > > We are using GE 6.2u5. > > Many thanks, > Richard > > > -- > Richard Ems mail: [email protected] > > Cape Horn Engineering S.L. > C/ Dr. J.J. Dómine 1, 5º piso > 46011 Valencia > Tel : +34 96 3242923 / Fax 924 > http://www.cape-horn-eng.com > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
