On the client side, if you set export DAVIX_DISABLE_REDIRECT_CACHING=True, does it work?

Manual tests without it as well right now:

gfal-copy -p -v -f -K adler32 --checksum-mode both --copy-mode pull davs://<src> davs://xrootd.phy.bris.ac.uk:1094/xrootd/cms/<dst>

With the latest upgrades (see #1736 (comment)) things started to work for the manual tests.

The diff between the logs for unmodified and DAVIX_DISABLE_REDIRECT_CACHING=True: the latter does not contain the line

DEBUG Davix: Add cached redirection <HEAD davs://xrootd.phy.bris.ac.uk:1094 ...

But if I take the line at face-value, it looks like the correct thing. The FTS debug log also contains a line like that.

Anyway, client-side changes are not useful to me as I have no control over what FTS does and since FTS serves a lot of sites they will not change their settings for just one. We tried fts-cms.cern.ch and lcgfts3.gridpp.rl.ac.uk and the only difference is the timeout time for the checksum request - 15min vs 9 min respectively.

We also have dteam enabled, if you want to have a go: davs://xrootd.phy.bris.ac.uk:1094/xrootd/dteam.


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

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