Print

Print

@alrossi : OK, I see what you are saying, yes the checksum query was going directly to the pool, to the same data server that was the target of the TPC (but on a different connection). It is implemented this way so it can work with vanilla xrootd redirectors. For example, EOS is handling this type of requests by redirecting to the head node (MGM).
(maybe what I wrote in my previous comment was misleading, please disregard it)

A side question, how is dCache handling kXR_stat requests send to the door, are they redirected to the pool, or resolved directly at the door?

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

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