Print

Print


Hi @simonmichal,

Would there be any problem with back-porting commit 9fb8851 to the stable-5.0.x branch, so it could be included in the next v5.0 release?

To be honest, the patch sounds (to me) like a bit of a hack: xrdcp's current behaviour seems to be perfectly spec compliant. Therefore, I would like to provide a better solution within dCache: one that doesn't require xrdcp to "tip-toe" around like this. Although the patch solves this specific issue, the problem could come back in the future under a different guise.

From reading the xroot spec, I believe that if dCache returned a token (as part of the kXR_redirect response) then the pool would be able to support all requests without returning this error. The pool would always know from which door the client came (via the token) so, for any query the pool does not support, it can always redirect the client back to the door.

However, during my first steps in this direction I'm seeing inconsistent (and seemingly incorrect) behaviour. Sometimes xrdcp presents the door-supplied token during the subsequent kXR_login request; sometimes it uses some kind of default token. I haven't figured out what is causing this, so I cannot say if the problem lies in dCache, our xroot Java library (xrootd4j), or XrootD. Whatever the cause, It will require more time (and more work on my part) before this solution is ready.

Since your patch is available right now, (if there's no objection) my suggestion is that your patch be back-port so it will be include with v5.0.4. For me, doing this would close this issue, and removes the immediate pressure to find a solution.

Meanwhile, I can try to understand what's going wrong (for me) with redirects and login tokens. I would then open a fresh issue if that work leads to any concrete questions about the xroot spec or XrootD.

Cheers,
Paul.


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-744560461", "url": "https://github.com/xrootd/xrootd/issues/1359#issuecomment-744560461", "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