LISTSERV mailing list manager LISTSERV 16.5

Help for XROOTD-L Archives


XROOTD-L Archives

XROOTD-L Archives


XROOTD-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

XROOTD-L Home

XROOTD-L Home

XROOTD-L  July 2012

XROOTD-L July 2012

Subject:

Re: Getting data from USCMS XRootD Federation Monitoring in machine-readable format

From:

Julia Andreeva <[log in to unmask]>

Reply-To:

Support use of xrootd by HEP experiments <[log in to unmask]>

Date:

Sun, 22 Jul 2012 08:24:51 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (212 lines)

Thanks a lot, Matevz.

Cheers
Julia
________________________________________
From: Matevz Tadel [[log in to unmask]]
Sent: 22 July 2012 08:31
To: Julia Andreeva
Cc: Daniel Dieguez Arias; [log in to unmask]
Subject: Re: Getting data from USCMS XRootD Federation Monitoring in machine-readable format

Hi Julia,

On 7/21/12 2:25 AM, Julia Andreeva wrote:
> Hi Matevz,
> Thank you very much for the detailed answres.
>
> See my comments/answers inline
> ________________________________________
> From: [log in to unmask] [[log in to unmask]] on behalf of Matevz Tadel [[log in to unmask]]
> Sent: 20 July 2012 20:20
> To: Julia Andreeva
> Cc: Daniel Dieguez Arias; [log in to unmask]
> Subject: Re: Getting data from USCMS XRootD Federation Monitoring in machine-readable format
>
> Hi Julia,
>
> On 07/20/12 02:00, Julia Andreeva wrote:
>>
>>
>> Hi Matevz,
>>
>> I asked Daniel, to use next time the xrootd mailing list. I think I did not get
>> confirmation that my subscribtion was approved, let's see whether it works.
>>
>> I have couple of questions:
>> 1)
>> What is shown on the Monalisa display:
>
> ML shows the summary monitoring information -- this is what xrootd servers
> report themselves about their status and activity.
>
> I also sent to Daniel a link to the CHEP paper (being reviewed) that desribes
> what we do:
> http://uaf-2.t2.ucsd.edu/~matevz/CHEP2012-S-12-00218.pdf
>
>> Only remote access?
>> Mixture of remote and local?
>
> This is a bit tricky :) as the summary monitoring information is completely
> oblivious about individual connections ... it just tells how much data any given
> server sent out ... and then we aggregate this by site to make dashboard plots.
> This is a complementary view to what is provided by detailed monitoring and
> file-access reports -- we see it more like a server/site performance/monitoring
> database we can use to drill down into in case of trouble. Also, our alarm
> system is based on that ... for almost a year now, the only thing that still
> happens every now and then is authentication problems (servers with bad certs,
> LDAP or GUMS issues). But since the new client knows how to reconnect in case of
> auth trouble, these errors do not show in failing jobs.
>
> We have a couple of sites that also use xrootd for internal access, University
> of Wisconsin being the major one (they have several clusters at the uni and they
> use HEP cluster to serve the data). UW then configured their internal access to
> go via different redirector/servers (easy as they use hadoop) and so we can
> separate internal and external access also in the summary monitoring.
>
> Another site like this is MIT ... I'd say practically all of their traffic is
> internal but we don't / can't separate this in the summary monitoring.
>
> Now, a very special case is the Omaha cluster which connects to Nebraska servers
> via a private sub-net (not exactly sure how network is configured). This access
> looks like it is local to UNL but in fact it travels about 100km north. So, I'd
> say, in this case the summary monitoring is more correct.
>
>
> -------
> OK, now I understand.
> -------
>> 2)
>> In order to decouple local access from the remote one, as a first approximation,
>> would it be enough to consider transfers which have the same domain for client
>> and server to be local , and all other cases to be remote?
>
> Yes, from detailed monitoring one can do that ... with the caveat for Omaha above.
>
> ---------
> Is there any other way to decouple Omaha access (certain pattern in the hostname for Omaha nodes for example?)
> ---------

At the moment, it is:
client_host=128.111.134.10
client_domain=unl.edu
As I said, I'm not exactly sure how the network is configured ... and I do find
it a tad strange that all hosts report exactly the same ip address.

>> 3)
>> According to my knowledge, Monalisa repository provides a way to subscribe to
>> any information which is in the repository, we were thinking to use this
>> possibility in order to retrive data in the machine-readable format and to make
>> consistency checks with data we get from ActiveMQ (when file is closed) and
>> aggregate on our side. But for this purpose we really need to understand what is
>> shown as a throughput on the ML display.
>
> If you know how do that, that makes the most sense, sure. We can also ask ML
> people for help.
>
> About consistency ... we produce daily reports from file-access reports (from
> OSG Gratia, same thing that also gets sent to CERN ActiveMQ) and the results are
> consistent with what is shown in ML. In fact, the inconsistency of these two
> lead us to extend/improve xrootd detailed monitoring about a year back (major
> thing was that vector-reads requests were not reported in the detailed monitoring).
>
> Actually ... why do you want to repeat these cross-checks?
>
> --------
> Crosschecks is for our system. We need to make sure that what we show on the Dashboard UI is correct.
> Daniel made a good progress in integrating of the xrootd transfer in the Global WLCG Transfer Dashboard.
> This is ou usual practice , before making system available for pilot users, to run consitency checks with some
> relevant information source. The only possibility we were thinking of is UCSD ML repository.
> May be we can also use Gratia reports, is there any documentation of how we can get them?

I know about this page from Gratia:

http://rcf-gratia.unl.edu/gratia/xml/facility_transfer_volume?exclude-vo=NONE&protocol=xrootd
There is the "download as csv" option at this page. I can investigate how to
extract other data (the schema is rather arcane). I'll send you an example of
our (uscms) auto-generated daily mail report (it contains user information so
it's not entirely public).

A nice weekend, to you, too ... well ... at least what's left of it :)

Cheers,
Matevz

>
> Have a nice weekend
>
> Cheers
>
> Julia
>
>
> Cheers,
> Matevz
>
>>
>> Thank you
>>
>> Cheers
>>
>> Julia
>>
>> On Fri, 20 Jul 2012, daniel dieguez arias wrote:
>>
>>> Hi Matevz,
>>>
>>> Thanks for the information. I add Julia to the cc.
>>>
>>> Cheers,
>>> Daniel.
>>>
>>> On 07/20/2012 01:04 AM, Matevz Tadel wrote:
>>>> Hi Daniel,
>>>>
>>>> On 07/19/12 06:48, daniel dieguez arias wrote:
>>>>> Dear Matevz,
>>>>>
>>>>>
>>>>> I am Daniel Dieguez. Currently I am working in WLCG Tarsnsfers Dashboard. In
>>>>> order to make consistency checks between WLCG and USCMS XRootD Federation
>>>>> Monitoring, it would be nice to get data from USCMS in machine-readable format.
>>>>
>>>> I suspect you get the data from UCSD monitoring via popularity, the thing
>>>> we're doing with Domenico, right?
>>>>
>>>> Are you aware of the differences between XRootD summary monitoring (what is
>>>> shown in MonALISA) and the XRootD detailed monitoring that sends out the
>>>> file-access reports at file close-time? I mean ... are you aware that you
>>>> will not get comparable results as in MonALISA we separate internal transfers
>>>> within Univ. of Wisconsin, which can be more than 1 GByte/s. We are trying to
>>>> get other sites (MIT, most importantly) to do the same, but this isn't
>>>> entirely trivial to setup so T2 admins tend to avoid this topic.
>>>>
>>>>> Currently I am looking at the plots shown on
>>>>> http://xrootd.t2.ucsd.edu/dashboard/
>>>>>
>>>>> Could you, please, guide me, how could I get output in csv , xmk or json?
>>>>
>>>> Hmmh, this comes from a Postgres DB of MonALISA ... I could give you a DB
>>>> dump, I think it was ~10GB the last time I checked if backups are being made :)
>>>>
>>>> Cheers,
>>>> Matevz
>>>> .
>>>>
>>>
>>>
>
> ########################################################################
> Use REPLY-ALL to reply to list
>
> To unsubscribe from the XROOTD-L list, click the following link:
> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1
>


########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
July 2009
June 2009
May 2009
April 2009
March 2009
January 2009
December 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use