@ccaffy Now that the other issue is done, could you please elaborate on
>If that's the case, I got the similar issue with a "redirector-server setup". I had to tell Davix to not use the redirection cache because Davix sent a HEAD request on the redirected server instead of the headnode....
I've summarized what you said and what we observe in this graph:
```mermaid
sequenceDiagram
autonumber
davix client->>+redirector: Do a TPC (pull)
redirector->>+server: Do a TPC (pull)
server->>+davix client: will do
loop status update
server->>davix client: transferred x bytes out of N
end
server->>+davix client: copy is done
note right of davix client: Let's reuse session cache
davix client->>+server: give me the checksum
note left of server: unknown connection (not from redirector)
note right of davix client: timeout after 15min
```
There are two unknowns to me:
1. Why do the transfers succeed 5% of the time (or when I run them manually)
2. Is there a way to change the behaviour on the server side (`tlsreuse`, full auth on server, etc).
The random successes or low-volume, successful tests are the most confusing bits.
The reason I am curious about 2. is that disabling the session cache on the client is out of my reach for the FTS.
My full config is here:
- [xrootd-clustered.cfg](https://github.com/BristolComputing/xrootd-se/blob/main/etc/xrootd/xrootd-clustered.cfg)
- config.d
- [10-file-catalog.cfg](https://github.com/BristolComputing/xrootd-se/blob/main/etc/xrootd/config.d/10-file-catalog.cfg)
- [10-hdfs.cfg](https://github.com/BristolComputing/xrootd-se/blob/main/optional/etc/xrootd/config.d/10-hdfs.cfg)
- [20-https-and-security.cfg](https://github.com/BristolComputing/xrootd-se/blob/main/etc/xrootd/config.d/20-https-and-security.cfg)
- [50-monitoring.cfg](https://github.com/BristolComputing/xrootd-se/blob/main/etc/xrootd/config.d/50-monitoring.cfg)
- [90-logging.cfg](https://github.com/BristolComputing/xrootd-se/blob/main/etc/xrootd/config.d/90-logging.cfg) [Note: currently running with `*.trace. all`, so online version differs)
--
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/issues/1736#issuecomment-1313902710
You are receiving this because you were mentioned.
Message ID: <[log in to unmask]>
########################################################################
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
