URL:
<http://savannah.cern.ch/bugs/?95234>
Summary: Xrootd delays 4 seconds dirlist requests
Project: XROOTD
Submitted by: furano
Submitted on: 2012-06-08 14:59
Severity: 3 - Normal
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Fixed by commit(s):
_______________________________________________________
Details:
Hi,
testing the DPM-xrootd frontend in the EMI testbed David and I realized that
there's an issue
with dirlist that is reproducible with a plain vanilla xrootd data server.
What an user sees through the command line interface is that his dirlist
request takes 4 seconds
to get an answer. This is due to a nasty interaction between:
1- the client invoking locate(*) even on data servers
2- the data server returning its own IP address as a response
3- the client interpreting this as a different server
4- the client killing its own previous session (still active, server
kxr_waits the client 4 seconds) and connecting again
I attach the client log that shows this.
Cheers
Fabrizio
_______________________________________________________
File Attachments:
-------------------------------------------------------
Date: 2012-06-08 14:59 Name: dirlist_delay.txt Size: 22kB By: furano
<http://savannah.cern.ch/bugs/download.php?file_id=26746>
_______________________________________________________
Reply to this item at:
<http://savannah.cern.ch/bugs/?95234>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
########################################################################
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
