New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xrootd per site statistics #7056
Xrootd per site statistics #7056
Conversation
bbockelm
commented
Jan 6, 2015
This service keeps per-site statistics from the Xrootd layer. Previously, the IO statistics were kept by the StatisticsSenderService on a per-file level. These are less-useful now that Xrootd reads from multiple servers (and possibly multiple sites) at a time! Currently, this has to be enabled manually and only outputs to the FJR. Long-term, we plan on adding additional statistics and additional output mechanisms (correcting the now-broken StatisticsSenderService reports we send to the Dashboard). NOTE: there is some trickery here due to the fact that the service registry is only available on CMSSW-managed threads. In order to make the service available from the callback threads, the service pointer is cached by the request manager object.
A new Pull Request was created by @bbockelm (Brian Bockelman) for CMSSW_7_4_X. Xrootd per site statistics It involves the following packages: Utilities/XrdAdaptor @cmsbuild, @Dr15Jones, @ktf, @nclopezo can you please review it and eventually sign? Thanks. |
{ | ||
edm::ParameterSetDescription desc; | ||
desc.setComment("Report Xrootd-related statistics centrally."); | ||
desc.addUntracked<bool>("reportToFJR", true) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no such parameter used in the code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shoot, I forgot to hook that up. Will update that in the next commit or so.
In particular, - We actually use the pset description to determine whether stats are kept. - State information is kept in a singleton, rather than passing a service pointr between objects.
Pull request #7056 was updated. @Dr15Jones, @ktf can you please check and sign again. |
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs unless changes or unless it breaks tests. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @ktf, @smuzaffar |
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @ktf, @smuzaffar |
+1 |