The bug is related to the bdii lookup for auto-lfc host determination.
defining manually the LFC_HOST variable can be a temporary workaround.
Adrien
Le 12/09/2012 15:34, Mario Kadastik a écrit :
>>> We have a large installation (ca 4000+ cores) with EMI-2.2 installed in Estonia. The bug did affect us and to get past it we made a small fix setting one environment variable for OPS tests. However for us the only two VO's are CMS and OPS and CMS doesn't use lcg-cr etc so the bug doesn't affect it and the environment variable fix was only to make ops tests happy. If you have VO's that use lcg-cr, then of course you're screwed.
>> As far as I know CMS uses lcg-cp within CRAB2 for staging out user files. I did not look into the details of the bug. Almost for sure it does not apply for the CRAB use case, which neither uses the BDII nor the LFC together with lcg-cp.
>>
>> Some testing of CRAB at the Estonia site was successful at least.
>
> Precisely. The bug as far as I understand only is there if you attempt lcg-cr with bdii lookup. The use case of CMS is lcg-cp and no bdii therefore no problem (I've done hundreds of CRAB jobs for my own analysis and it works).
>
> Mario Kadastik, PhD
> Researcher
>
> ---
> "Physics is like sex, sure it may have practical reasons, but that's not why we do it"
> -- Richard P. Feynman
|