Difference between revisions of "Tools/Manuals/TS109"

From EGIWiki
Jump to: navigation, search
(Further documentation)
Line 1: Line 1:
 +
 +
{{Template:Op menubar}}
 +
{{Template:Doc_menubar}}
 +
[[Category:Operations Manuals]]
 
{{TOC_right}}
 
{{TOC_right}}
[[Category:FAQ]]
 
 
------
 
------
 
Back to [[Tools/Manuals/SiteProblemsFollowUp|Troubleshooting Guide]]
 
Back to [[Tools/Manuals/SiteProblemsFollowUp|Troubleshooting Guide]]

Revision as of 12:25, 23 November 2012

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators



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"

Further documentation