Hi Danny, thank you for the quick reply. I didn't know ResvOverRun. But in addition it would be nice, if we could say "don't accept jobs where --time is too long", so that the job would be rejected like if the user specified a wrong reservation name. The user would then ask the admins to extend the reservation.
Otherwise, since users (and admins) don't always care about details, a job might be cancelled after being executed some days, or if we set ResvOverRun, we can't be sure that the resources become available at the desirable end time. Best regards Igor On Thu, 16 Feb 2012 08:48:03 -0700 Danny Auble <[email protected]> wrote: > > Please see man slurm.conf look for the ResvOverRun option. What you are > seeing is expected by default. > > Danny > > On 02/16/12 06:54, Igor Geier wrote: > > The [email protected] list will soon be retired. The schedmd.com > > domain will host its replacement. > > > > http://www.schedmd.com/slurmdocs/mail.html > > > > The new list is now operational. Please resubmit this message to > > [email protected] > > > > The archive of the slurm-dev list will remain here: > > http://groups.google.com/group/slurm-devel. Postings to the new list will > > be archived to the same place. > > > > Dear all, > > > > we are using 2.3.3. When a reservation reaches its EndTime, jobs running > > inside that reservation are cancelled. Is this the standard behavior? > > > > I think, for us, it's better not to start jobs with time> reservation > > time, or to print a warning for the user (a warning might be overseen > > though, since some users submit their jobs by scripts). > > > > Best regards > > > > Igor > > -- Igor Geier -------------------------------------- Center for Scientific Computing (CSC) University of Frankfurt Max-von-Laue-Straße 1 60438 Frankfurt am Main +49(0)69/798-47353 [email protected] http://csc.uni-frankfurt.de/ --------------------------------------
