Am 01.08.2011 um 18:52 schrieb Francesco Minafra: > On 1 August 2011 18:16, Reuti <[email protected]> wrote: > > > No. Advance reservation and resource reservation are two different things. An > advance reservation starts at a certain time in the future (once it's > granted), but for an advance reservation no predication can be made right > now, although it's on the wish list of the users for some time. > > > Ok, clear. Is there a way to monitor the _resource_ reservation? Something > similar to qrsub or the monitoring log..
No. This would be a long term goal to get some real time features into SGE. I.e. submit with a resource reservation and SGE will tell you want the job will start at latest. > >> For a resource reservation to work, it's also mandatory to submit jobs > >> with reasonable h_rt/s_rt requests. Otherwise the default in the scheduler > >> will be taken and due to the default "infinity" may avoid any reservation. > >> > > > > the job was submitted with a well defined value of hard runtime, i.e. > > h_rt=600 > > All jobs are requesting an individual h_rt? > > > No, other jobs are not requesting an h_rt but are using the default one, > which is 24 hours. Where do you set the default? in $SGE_ROOT/defaultcomm/sge_request? > And your setting of default_duration is ... > > default_duration INFINITY I would suggest to change this to 9999:00:00 -- Reuti > Best regards, > Francesco. > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
