Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Tools/Manuals/TS109"

From EGIWiki
Jump to navigation Jump to search
(Created page with '{{TOC_right}} Category:FAQ ------ Back to Troubleshooting Guide ------ = gstat2 Cores format is wrong = == Error == All or some of: …')
 
Line 19: Line 19:
Each GlueSubCluster object should contain a value for the
Each GlueSubCluster object should contain a value for the
<font face="Courier New,Courier">GlueHostProcessorOtherDescription</font> attribute indicating at least
<font face="Courier New,Courier">GlueHostProcessorOtherDescription</font> attribute indicating at least
the average number of logical cores per WN and possibly the corresponding
the average number of logical cores per physical CPU and possibly the corresponding
<font face="Courier New,Courier">HEP-SPEC06</font> benchmark value per core.  At least <font face="Courier New,Courier">WLCG</font> sites
<font face="Courier New,Courier">HEP-SPEC06</font> benchmark value per core.  At least <font face="Courier New,Courier">WLCG</font> sites
should run that benchmark and publish the resulting value(s).
should run that benchmark and publish the resulting value(s).

Revision as of 17:08, 25 September 2011


Back to Troubleshooting Guide


gstat2 Cores format is wrong

Error

All or some of:

ERROR: some-ce.some-domain, The Cores format is wrong, Cores not set
ERROR: some-ce.some-domain, The Benchmark format is wrong, Benchmark not set
ERROR: some-ce.some-domain, The Cores format is wrong, Unspecified number of cores

Diagnosis

Each GlueSubCluster object should contain a value for the GlueHostProcessorOtherDescription attribute indicating at least the average number of logical cores per physical CPU and possibly the corresponding HEP-SPEC06 benchmark value per core. At least WLCG sites should run that benchmark and publish the resulting value(s). Example:

GlueHostProcessorOtherDescription: Cores=4,Benchmark=8.15-HEP-SPEC06

Note that the number of cores need not be an integer when the subcluster is somewhat inhomogeneous:

GlueHostProcessorOtherDescription: Cores=5.0502,Benchmark=14.5626-HEP-SPEC06

Solution

Run the benchmark (if applicable) and define a YAIM site-info.def variable in the corresponding format:

CE_OTHERDESCR="Cores=N.M,Benchmark=X.Y-HEP-SPEC06"

or just

CE_OTHERDESCR="Cores=N.M"