Hi Oliver,
Sounds like a good plan. Please go ahead and see if either setting makes a
difference. Technically, not using a session cache is supposed to
substantially increase reconnect latency as the client has to redo all the
negotiation. On the other hand, a reconnect with a session cache does not
provide the client's certs. This doesn't matter for stict token based
authorization but, obviously, fails for any kind of x509 authentication.
Andy
On Fri, 17 Jul 2020, Oliver Freyermuth wrote:
> Hi Andy,
>
> many thanks to you for hunting the bear down so quickly from such an unclear error situation ;-).
> I'm also completely for keeping the directive.
> While I did not see cases of https://github.com/xrootd/xrootd/issues/1177 again in my tests with the test node even with activated session cache, I wonder whether these kinds of failures will reappear in production.
> So I'd tend to the cautious side, and indeed think that turning the session cache off by default is best for now.
>
> What I will do in any case is to try enabling the session cache in production again (once the next release is out) and watch the situation for a few days. If https://github.com/xrootd/xrootd/issues/1177 really does not reappear, we may rethink and change the default to activating the cache by default.
>
> What do you think?
>
> Cheers,
> Oliver
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1252#issuecomment-660250665
—
You are receiving this because you are subscribed to this thread.
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/1252#issuecomment-660427240",
"url": "https://github.com/xrootd/xrootd/issues/1252#issuecomment-660427240",
"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