@simonmichal Hi!
well, i could not properly asses the difference between:
Default value for the time after which an error is declared if it was impossible to get a response to a request.
and
Default value for the time after which a connection error is declared (and a recovery attempted) if there are unfulfilled requests and there is no socket activity or a registered wait timeout
hence i choose the REQUESTTIMEOUT instead of STREAMTIMEOUT
My intent was: if the redirector(and server) cannot answer and allocate/initiate the request, then fail (there is no point to wait for an overloaded/unresponsive server), to be able to move to next replica.
So, what would be the best setting for my intent above? also, i would argue against non-recoverability: given that i (can) have multiple replica in a metafile, why should be unrecoverable? just fail on the particular request, move to next replica if any, then respect the -retry parameter if any ..
Thanks a lot!


Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1597/1061994960@github.com>

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