 |
 |
Hi Lukasz, On 12/16/11 01:30, Lukasz Janyst wrote: > Hi Matevz, > > 2011/12/15 Matevz Tadel <[log in to unmask]>: >> We ((US)CMS) are thinking about sending custom session information from xrootd >> jobs via the user-info detailed monitoring messages (the 'i' message). Andy said >> he suspects that the interface to do this is not available in the "old" client. > > well, I definitely don't want any kind of a "dial home" mechanism > in the client itself, this kind of stuff annoys people (it would annoy > me). We could, however, think of some sort of a plug-in mechanism > which would allow you to load your own monitoring library and do > whatever you want there. The client API still should implement part of the xrootd protocol that allows applications using it to send custom monitoring information, no? In any case, all your secrets (DN, machine you are connecting from, files you are opening) are already available in the monitoring stream. What I'm after is the request-id kXR_set with "monitor" argument that calls XrdXrootdProtocol::do_Set_Mon() which then sends the application provided string + dict_id to the monitoring stream. This is implemented on the server, but not in the client. Implementation of passing of the info-traces using the dict-id generated by the above request seems to be missing from both the server and the client, though. I don't think we need this, at least not for the first iteration, as all we want to pass is CMS job-id once a file-open succeeds. This will allow us to correlate information from job-submission DBs and from the xrootd monitoring data -- mostly to dig down on failures and for debugging. Cheers, Matevz > Currently, there is a monitoring hook in xrdcp that could be loaded > from a custom library [1]. It should probably be extended/rewritten to > give you access to more information, and probably some hooks should be > put here [2] as well. > >> As CMS will probably use the old client throughout 2012 I'd be willing to get it >> implemented for the next 3.X release. Does this sound good to you? > > Sure. Don't hesitate to contact me if you need more info. > >> Writing this I realized I don't really know what's the status of the new client >> and at what point it will get pushed into the releases. Will this be 4.X? > > It's going slower than expected, unfortunately. Both because the > task turned out to be more complex than expected and because my > attention gets constantly preempted by something. I plan to have the > API level (without caching stuff) ready shortly after the CERN > Christmas break, and then work through January and February on the > tools (xrdcp, xrd...) and caching. > > Lukasz > > [1] http://xrootd.cern.ch/cgi-bin/cgit.cgi/xrootd/tree/src/XrdClient/XrdClientAbsMonIntf.hh > [2] http://xrootd.cern.ch/cgi-bin/cgit.cgi/xrootd/tree/src/XrdClient/XrdClient.cc#n1966 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1