Thanks for this reply.
For what concerns gpfs, these 4 hosts are not doing anything apart from accessing filesystem for XrootD service. We do monitor gpfs filesystem and there was no overload which could block or slow down access to filesystem when XrootD threads were hanging.
gpfs has the ability to recall files from tape but not via xrootd; the Xrootd instances of CMS have no plugin to interact with tapes.

Following your suggestions, we installed xrootd-debuginfo, set again 2048 as maximum threads, and we are waiting for hanging threads to happen :-)
Then we'll use gdb as you said and send you a link.

Thank you very much for your help,
lucia

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

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