Hi Andy,

the problem here is really a mismatch of architectures between Castor and XRootD. The castor-xrootd plugin always stalls the client because it needs to wait for a response from Castor. Now, if the client disconnects, the castor request needs to be explicitly aborted in order not to abuse the throttling mechanism in Castor. Would it be possible, to use something like ::Delete( reason ) instead of the destructors?

Cheers,
Lukasz

—
Reply to this email directly or view it on GitHub.

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