 |
 |
Hi @bbockelm, We've previously been using the xrootd-hdfs built-in implementation, but due to the time outs we tried our own solution (since we can now store in xattr). But this did not help. We are allowing for 100 simultaneous checksums and as far as I can see, neither redirector nor server come ever close to that limit. 2GB files take around 15s, so the largest files (~8GB) should not take much longer than 1 minute. Nothing close to the 15min FTS sees. The checksum log is updated relatively slowly → not many requests per minute. It is hard to map 1:1, but it looks like we get a request at `13:37:30`, checksum script returns result at `13:37:35` (was stored in xattr for this example), but we still see a timeout. Is there a way to follow a connection through the logs to get a more accurate reading on the situation? How did you figure out the congestion on your side? -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1736#issuecomment-1185510707 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