We've been running Maui/Torque for quite a few years here. On our latest cluster there has been a need to start using preemptive queues (classes). This has done fine except for a problem we had when setting a system reservation.
So a system reservation was set across the entire cluster. Normally, on clusters without preemptive scheduling, jobs exceeding the wallclock time will block, allowing other shorter jobs to backfill in. When using a preemptive class, when a job exceeeds available wallclock time, it remains in the IDLE state preventing other backfill jobs from running. Yes, these other jobs are preemptee class. Manually placing the overruns on hold allows these other jobs to get scheduled. Am I simply missing something in the configuration? Or is this the expected behavior when using preemptor/preemptee classes/QOS? Thanks, Bill _______________________________________________ mauiusers mailing list [email protected] http://www.supercluster.org/mailman/listinfo/mauiusers
