Print

Print

@abh3 Sorry, I can't quite reproduce the hanging problem. I can re-create the xrootd "initialization failed" condition, but in this case, xrootd terminates. With xrootd down, requests to the data node time out.

Previously, we observed that the redirector sent requests to data nodes that had experienced initialization failure, and the requests failed. That's how we noticed all these issues in the first place. I haven't been able to reproduce that behavior now.

Since we will be changing our configuration to disable the persist option, I think all these issues will be prevented at our site in the future. It seems these problems occur because persist was enabled by default in multi-user mode, which, you say, is not supported. It would be good if multi-user mode would automatically disable both chkpnt and persist so these errors would not be able to occur.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1721/1186013743@github.com>

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