Hi Matevz,
The issue here is that the redirector is under no obligation to re-pass
opaque information. The only thing it can do is to add additional opaque
information. It's the client's responsibility to maintain the "tried"
history. I don't think the old client does this and drops the history at
some point (so, yes, it's a bug). The new client did much the same but that
is being corrected in 4.1.
Andy
-----Original Message-----
From: Matevz Tadel
Sent: Tuesday, September 30, 2014 2:56 PM
To: xrootd-dev
Cc: Jeff Dost
Subject: tried= ignored on redirection
Hi,
While running the xrootd-hdfs-fallback at UCSD where we rely on
tried=xrootd.t2.ucsd.edu to get files served from elsewhere (as we know they
are
corrupt at ucsd) we observed that sometimes the proxy still gets redirected
back
to UCSD.
I managed to reproduce this behaviour with xrdcp, two logs attached. The
first
one is simpler and should be enough, the second one just has an extra
redirection to CIEAMT where the authentication fails.
It seems tried= gets lost right at the start when the client is passed from
xrootd.unl.edu to cms-xrd-global and is set to
[tried=+1213cmsxrootd1.fnal.gov1213xrootd.unl.edu]
Are we (CMS) doing something wrong here? Are redirectors really allowed to
drop
opaque parameters?
But given that the tried= generated by the redirector looks rather fishy we
might be in luck and this is just a bug somewhere :)
Matevz
########################################################################
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
########################################################################
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
|