 |
 |
Hi Yujun, The way you solve this problem is to visit the preferred places first. So, in this case you would send the client to the dCache XRootD redirector and if it does not have the file it would send the client to the EOS XRootD redirector. Now, I am assuming that this is the way it is setup. If not, then we may need a different plan. Andy On Fri, 22 Apr 2022, Yujun Wu wrote: > Good morning. > > Could XRootD developers/experts help us with a special situation? > > We have two xrootd redirectors reporting to a higher-level redirector: > > > 1. Level 1: EOS XRootD redirector > 2. dCache XRootD redirector > > 2. Level 2: Site redirector > > User requests contact our site redirector and then the site redirector redirects the requests to either EOS XRootD redirector or dCache XRootD redirector. When a file is located in either EOS or dCache side, things are working as expected. However, when a file is located on both EOS and dCache, it seems EOS redirector is always chosen instead of dCache redirector. This is not ideal for us as we want to the files to be accessed from dCache XRootD redirector first. > > Could you please tell if there is a way in XRootD configuration file(s) to specify the order/priority when a user request comes in? > > Thanks in advance for any advice on this. > > > Regards, > Yujun > > ######################################################################## > Use REPLY-ALL to reply to list > > To unsubscribe from the XROOTD-L list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1 > ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1