On 05/25/2012 11:31 AM, Daniel Gruber wrote: > 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).
But I thought exactly *that* is what reservations were meant to *solve*. That free resources get reserved for a job A, asking for a reservation, so that other jobs with lower priority which *wouldn't end* before job A - because of s_rt and/or default_duration settings - don't get started on that *reserved* resources. Isn't this the way resource reservation is supposed to work? Or is the mixing of different PEs the culprit of me not understanding it? 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
