Are mynode{17-24} in a queue that is configured to use your "threads" PE?
Ian
On Tue, Mar 12, 2019 at 8:58 AM David Trimboli <trimb...@cshl.edu> wrote:
>
> On 3/12/2019 11:43 AM, Reuti wrote:
>
> Now a followup question. I implemented this rule to ensure that no single
> user takes more than 90% of our available slots:
> {
> name limit90percent
> description NONE
> enabled TRUE
> limit users {*} to slots=536
> }
>
> (Our cluster has a total of 596 slots.) This worked fine until someone tried
> to submit a parallel environment job with the -pe option. On 16 out of our 24
> nodes, it still worked. But if they sent a job hard-queued to one of the
> upper nodes 17–24, it would never run, with this in the scheduling info:
>
> What was the submission command? A plain '-q upper'? There was/is an issue
> where you have to specify instead '-q "*@@upper"' for a hostgroup named
> @upper. Or one can try to have a dedicated PE only for the upper nodes and
> request this PE (i.e. in the queue configuration "pe_list …,[@upper=upper]".
>
> The following will fail:
>
> qsub -l vf=1G -l
> h="mynode17|mynode18|mynode19|mynode20|mynode21|mynode22|mynode23|mynode24"
> -pe threads 1 anyscript.sh
>
> It'll work if you remove "-pe threads 1".
> _______________________________________________
> users mailing list
> users@gridengine.org
> https://gridengine.org/mailman/listinfo/users
>
--
Ian Kaufman
Research Systems Administrator
UC San Diego, Jacobs School of Engineering ikaufman AT ucsd DOT edu
_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users
