my current working theory is that in the meanwhile (meaning before the re-connect task was schedule) another request was issued on the same channel and restarted (immediately) the connection procedure

Michal and I chatted in person. This is certainly possible in the XCache use case as there was a large number of clients requesting a small number of files all on the same origin server. So, it's a good theory and I'd be able to test given a patch.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: <xrootd/xrootd/issues/1979/1488456702@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1979#issuecomment-1488456702", "url": "https://github.com/xrootd/xrootd/issues/1979#issuecomment-1488456702", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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