 |
 |
I don't think I have much insight but experience from experimenting it. I do use external script because this allows me to clearly see that checksum requests are piling up. My _GUESS_ from what I see is that when many checksum requests coming in, checksum calculation are actually slow (CPU limit or HD's priority to write over read? don't know). If a checksum is running, Xrootd (via HTTP or xroot protocol) will periodically update FTS. But if a checksum is not in running state (e.g. exceed the max checksum configured in xrootd), the xrootd won't update FTS with perf mark. In that case, FTS may timeout the transfer after 1 minute (and from the FTS logs I saw, all checksum timeout happened exactly after 1 minute). My only solution is to increase the max allowed checksums. -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1736#issuecomment-1188008947 You are receiving this because you commented. 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