 |
 |
> the maximum time lag of a request coming in from the gateway container on the worker node, and the response from echo is < 5 seconds. Certainly a lot less than 30 minutes One thing that you might have overlooked was an earlier request for logs when you see an operation timeout. What you posted above is only the "timeout" piece but it's not apparent _when_ the request started (was truncated). That said, there is something slightly funny in the server messages you post: > Jul 22 07:51:14 lcg2160 docker: 200722 06:51:14 4146 XrdLink: Unable to send to u41.7:4308@localhost; broken pipe @abh3 - shouldn't the client be shutting down the connection cleanly? Seems strange it just would end like that... similarly, it's strange that each file processed is a separate connection (the Xrootd client aggressively reuses sessions). -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1259#issuecomment-664395915 ######################################################################## 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