Hi, > Am 14.07.2015 um 12:50 schrieb William Hay <[email protected]>: > > On Tue, 14 Jul 2015 09:10:58 +0000 > Alexis Huxley <[email protected]> wrote: > > >> then the output is: >> >> Tue 2015-07-14 10:55:32 CEST: sge_qmaster[42156]: >> get_load_value: attrname=slots Tue 2015-07-14 10:55:32 CEST: >> sge_qmaster[42156]: get_load_value: get_attribute_by_name(..., >> "slots", ...) failed Tue 2015-07-14 10:55:32 CEST: >> sge_qmaster[42156]: get_load_value: attrname=slots Tue 2015-07-14 >> 10:55:32 CEST: sge_qmaster[42156]: get_load_value: >> get_attribute_by_name(..., "slots", ...) failed >> >> So now I'm puzzled. Is there something special about 'slots' that >> means it's not defined in the normal way? This is a pristine >> installation, have I forgotten to configure slots somewhere? >> > 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.
"slots" was used for a long time for the load_formula to use least used or fill host strategy - without the necessity to change the complex definition. It's reported as a complex on a host level `qhost -F slots` AFAICS. -- Reuti > 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. > > How is slots defined on the hosts of your cluster? > > William > > _______________________________________________ > SGE-discuss mailing list > [email protected] > https://arc.liv.ac.uk/mailman/listinfo/sge-discuss
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ SGE-discuss mailing list [email protected] https://arc.liv.ac.uk/mailman/listinfo/sge-discuss
