On 6 December 2011 09:48, Reuti <re...@staff.uni-marburg.de> wrote: > Hi, > > Am 06.12.2011 um 10:04 schrieb William Hay: > >> 128 > 2147483648 >> >> A user has submitted a job requesting 128 slots: >> qstat -j producing the following output: >> parallel environment: qlc-[1ABCDEFGHIJTWKLMNOPX] range: 128 >> qalter -w v produces the following: >> Job 404311 cannot run in PE "qlc-H" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-X" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-A" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-W" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-F" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-P" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-O" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-1" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-J" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-D" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-K" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-M" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-L" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-I" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-N" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-B" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-E" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-C" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-G" because it only offers 2147483648 slots >> Job 404311 cannot run in PE "qlc-T" because it only offers 2147483648 slots > > yes, the output is more or less useless. They don't offer slots, as any limit > might be set there and so the job can't run therein. Better would be of > course if the output would tell you more about the real problem. Can you > please check: > > - qalter -w p <jobid> Produces much the same output as qalter -w v
> > - did you request memory or any other resource? Yes but we have other queued jobs which have more restrictive resource requests that are nevertheless obtaining reservations(as determined by examining the schedule file) while this job is not (which is why I started investigating it). I was suprised to see that the PE's were rejected because they only offered MAX_INT slots. Normally this sort of message contains a sensible number. > > >> Each pe is actually defined with 9999 slots the real limitation being per >> host. > > - but each PE on its own is offering 128 slots (as you can't collect slots > from different PEs by a wildcard) > > -- Reuti > > >> Other jobs seem to work fine. >> This appears to be preventing the job from gaining a reservation. >> >> Any suggestions? >> >> William >> _______________________________________________ >> users mailing list >> users@gridengine.org >> https://gridengine.org/mailman/listinfo/users > > > _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
