The number of slots is normally defined by the slots entry of a queue rather than via load sensors or via complex_values of a queue or host.
That I already have: te-ahux01# qconf -sq all.q | grep -i slot slots 1,[te-ahux02.rzg.mpg.de=4] te-ahux01#
For it to work in a load formula it would need to be reported via a load sensor or possibly in a host complex_values setting.
Ah, that was what I was missing!
te-ahux01# qconf -se te-ahux02 | grep -i complex_values
complex_values NONE
te-ahux01#
and then with it defined:
te-ahux01# qconf -sq all.q | grep -i slot
slots 1,[te-ahux02.rzg.mpg.de=4]
te-ahux01#
and now submitting a job can get the value:
Tue 2015-07-14 12:59:07 CEST: sge_qmaster[42156]: get_load_value:
attrname=slots
Tue 2015-07-14 12:59:07 CEST: sge_qmaster[42156]: get_load_value:
*dvalp=4.000000
Tue 2015-07-14 12:59:07 CEST: sge_qmaster[42156]: get_load_value:
attrname=slots
Tue 2015-07-14 12:59:07 CEST: sge_qmaster[42156]: get_load_value:
*dvalp=3.000000
How is slots defined on the hosts of your cluster?
Well, I had thought that the 'qconf -sq all.q' output above meant that it was defined where it was supposed to be defined, but you very clear answer shows I was missing the link to making it interrogatable. Excellent! Many thanks for the quick help! Alexis
<<attachment: alexis_huxley.vcf>>
_______________________________________________ SGE-discuss mailing list [email protected] https://arc.liv.ac.uk/mailman/listinfo/sge-discuss
