Hello.

I hope the causes of this have been understood now; I think it is a combination of things. One issue is that the transfer stalls and the other is question of it being restarting/recovering. I think the relevant difference between the xrdcopy and gfal2 case is that gfal2 typically adds the '?xrd.gsiusrpxy=' in the url. This causes some slightly different processing in the client library and in a roundabout way caused the stream to not be recovered after the timeout. This should be addressed in PR #1824. (The description in that PR doesn't really describe this case, but I think it does also cover the problem here).

The other issue - the transfers stalling - I hope will be addressed with PR #1829.

We'll likely discuss these PR in the xroot team somewhat, before including them or similar changes in a release, and then hopefully this issue (1808, and also 1739) should be fixed.


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

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1808#issuecomment-1315475939", "url": "https://github.com/xrootd/xrootd/issues/1808#issuecomment-1315475939", "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