Hello, Philip Peartree wrote:
> I have tested my system out, and it appears that if the time is not > specified, then it gets routed to the first queue (short_2h) despite > having queue_centric_limits enabled and a default walltime. If I try > to submit a job with a walltime of 336:00:00 directly to the short_2h > queue I get: > > qsub: Job exceeds queue resource limits MSG=cannot satisfy queue max > walltime requirement > > It appears as though torque is not applying the walltime default until > it has reached the execution queue, which my understanding of > queue_centric_limits says it should apply before the routing queue. > > Any ideas? Well, did you try my other suggestions? >> Another way would be to define the >> route_destinations the other way around, making sure to have >> resources_min and resources_max for all execution queues. If unspec is >> first, job with unspecified resource limits will go there first, >> regardless of the queue_centric_limits setting. >> >> Yet another way to make this work is to make sure that every job has a >> walltime limit. At our site, the default walltime limit is 0, so people >> have to specify it explicitly. You can however make sure that the limit >> is present by using a submit filter that adds a walltime limit to the >> script if it is not present. -- Michel Béland, analyste en calcul scientifique [email protected] bureau S-250, pavillon Roger-Gaudry (principal), Université de Montréal téléphone : 514 343-6111 poste 3892 télécopieur : 514 343-2155 RQCHP (Réseau québécois de calcul de haute performance) www.rqchp.qc.ca _______________________________________________ mauiusers mailing list [email protected] http://www.supercluster.org/mailman/listinfo/mauiusers
