Yes! We definitely could benefit from this on the CMS side!
Sent from my iPhone
> On Apr 15, 2019, at 5:21 PM, Matevz Tadel <[log in to unmask]> wrote:
>
> Hi,
>
> [This is mostly for Andy, Brian, and Michal.]
>
> In the context of XCache cluster used by CMSSW multi-source jobs there is an issue with cmssw jobs requesting opening of a second source on the cache cluster using the tried= opaque parameter to point to cache server already in use. This leads to creation of another replica of the same file in the cache cluster.
>
> The cache still needs to honor tried= in case there is a problem with the existing server. However, asking for a new "extra" server in the context of cache does not make much sense.
>
> To distinguish these two conditions I propose to introduce a new opaque directive, "using=", used to signal to the redirector that the client is already using the listed servers.
>
> On cmsd side this would be accompanied with a cms.dfs multisource count ("sister" option to cms.dfs retries). These two would then control how many errors and parallel accesses are allowed for a client session.
>
> Does this make sense?
>
> 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
