Hi Andy,
The whole trace had 91 entries ... the entry index is printed in the beginning
of each line below ... so it's between 8 and 20 read-writes in every window.
Cheers,
Matevz
On 08/23/11 15:59, Andrew Hanushevsky wrote:
> Hi Matevz,
>
> The flush will only happen if there is something to flush. How many events where
> in that window?
>
> Andy
>
> -----Original Message----- From: Matevz Tadel
> Sent: Tuesday, August 23, 2011 3:35 PM
> To: xrootd-l
> Subject: xrd.monitor - the flush parameter
>
> Hi,
>
> I'm looking into details of monitoring traces ... and I suspect that the flush
> parameter is not doing what the docs say.
>
> E.g., I have:
> xrootd.monitor all auth flush 30s mbuff 1472 window 5s dest files io info user
> xrootd.t2.ucsd.edu:9930
> and then I get a trace with the following windows:
> TTTT Shukaladunka N=91, from uaf-4.t2.ucsd.edu, seq=239
> 0: win 1314136743 1314136743
> 9: win 1314136743 1314136818
> 21: win 1314136818 1314136973
> 40: win 1314136973 1314137233
> 59: win 1314137233 1314137548
> 79: win 1314137548 1314137783
> 90: win 1314137783 1314137783
>
> The full message covers timespan of 1314137783 - 1314136743 = 1040s
> Shouldn't this be limited to 30s? [I realize this is a bit excessive.]
>
> The message got sent because the size limit, 1472 bytes, was reached.
>
> Cheers,
> Matevz
|