Hello, thanks a lot William. You point it out. My consumables are host consumables defined with the "YES" option. Changing to "JOB" resolved the issue. When I configured my parameters in the Complex, this option was not clear to me so I chose the more simple one. Now it is clear...
Thanks a lot cheers Lionel ________________________________________ De : [email protected] [[email protected]] de la part de William Hay [[email protected]] Date d'envoi : mercredi 19 septembre 2012 10:39 À : Lionel SPINELLI Cc : [email protected] Objet : Re: [gridengine users] RE : Customizing qstat display On 19 September 2012 09:11, Lionel SPINELLI <[email protected]> wrote: > Sorry for my previous email which was an error... > > I have a new concern on my grid I don't know how to resolve according to best > practices. > Since I have defined my two new user defined consumable parameters, some jobs > stay in pending state with the grid saying that "Cannot run in PE because it > only offers 0 slots" whereas no jobs are running on the nodes. > > I made some test to understand and there is a strange thing. If i submit a > job with > qsub -pe make 1 -l param1=1 -l param2=1 everything is fine (the PE have 64 > slots, param1 can go up to 90 and param2 up to 16) Consumables are associated with hosts, queue instances or the global pseudo-host not PEs. It's not clear where you defined these values. It's also not clear if your consumables are per slot or per job. Judging by your problem description you have it set per slot but want per job. > > It is also ok with: > > qsub -pe make 10 -l param1=1 -l param2=1 > qsub -pe make 1 -l param1=5 -l param2=1 > qsub -pe make 1 -l param1=1 -l param2=2 > > but the job stay in pending state with: > > qsub -pe make 10 -l param1=5 -l param2=2 The default rule for consumables (consumable set to YES) is to multiply the resource request by the number of slots assigned to each host so the above job would needs 20 units of param2 - more than you have available (at least on a single host). If you want the resource consumed per job you can set consumable to JOB which will only consume on the head node of a job. > > On PE, I use the $pe_slots allocation rule and on scheduler the "-slots" load > formula. On each host "slots" is defined to 15 because for me it was the > number of CPU used by the job indicated by the "-pe make X", but now, I am no > more sure on that. I though that maybe the "slots" contains also the used > consumable "10 + 5 + 2 = 17 > 15". Is it the case? Using this rule limits the job to a single host so it must get resources from one host. > If so one solution would be to define a third custom consumable indicating > the maximum number of CPU and use: > > "qsub -l param3 10 -l param1=5 -l param2=2" instead of "qsub -pe make 10 -l > param1=5 -l param2=2" > > but in that case what would be scheduler load rule to use? > Is there a better solution? > > Thanks for your advise. > > Lionel > > > > ________________________________________ > De : Lionel SPINELLI > Date d'envoi : mercredi 19 septembre 2012 09:54 > À : Reuti > Cc : [email protected] > Objet : RE : [gridengine users] Customizing qstat display > > ________________________________________ > De : Reuti [[email protected]] > Date d'envoi : mardi 18 septembre 2012 11:21 > À : Lionel SPINELLI > Cc : [email protected] > Objet : Re: [gridengine users] Customizing qstat display > > Am 18.09.2012 um 09:34 schrieb Lionel SPINELLI: > >> Hello all, >> >> I would like to know if there is a way to customize the display of the >> "qstat -f" command. Here is my point: I have defined in the complex two host >> related consumable parameters and I would like to see their consumption in >> the "qstat -f" display. This command already display the number of slots >> available and currently used. I would like to have a similar display for my >> user defined parameters. > > Try something like: > > $ qstat -F mem_free,virtual_free -f > > -- Reuti > > >> Is it possible? >> >> Thanks a lot in advance >> >> cheers >> >> Lionel >> _______________________________________________ >> users mailing list >> [email protected] >> https://gridengine.org/mailman/listinfo/users > > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users > > _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
