The problem, if it is as what the xrootd developer identified before, is a cache replacement issue of root client, which only happens if a job reads from xrootd servers directly. If a file is copied to batch node, this cache is not used. According to the developer, the offending file will _likely_ repeat the problem most of the time. I am not sure whether upgrading xrootd client package at site will help (it may). It is a little risky because the buggy root client is embedded in ATLAS releases. Using LD_LIBRARY_PATH at a site will modify a lot of things so we much be very careful. To solve the root of the problem, we need xrootd developers to work with the ROOT team and ATLAS.
**ACTION ITEM** Each site needs to provide a date before the end of June for their throughput test demonstration. Send the following information to Shawn McKee and CC Hiro: a) Date of test (sometime after June 14 when STEP09 ends and before July 1) b) Site person name and contact information. This person will be responsible for watching their site during the test and documenting the result. For each site the goal is a graph or table showing either: i) 400MB/sec (avg) for a 10GE connected site ii) Best possible result if you have a bottleneck below 10GE Each site should provide this information by close of business Thursday (June 11th). Otherwise Shawn will assign dates and people!!
Please note that this site is a content mirror of the BNL US ATLAS TWiki. To edit the content of this page, click the Edit this page button at the top of the page and log in with your US ATLAS computing account name and password.