@abh3, regarding the phantom session, I extrapolated that if the client gets `kXR_wait` as a reply to `endsess`, it should wait and try again, i.e. re-issue the endsess? Would that explain completely the problem?
If so, it is still worrying that the link could not be terminated in XrdXrootdProtocol::do_Endsess() one minute after establishement, and that more than one other minute after, the initial open finally got delivered. Would this mean the retry timing is dependent on the TCP session dying on its own? Could you kill the phantom/previous connection more drastically ("deep six" it as you were suggesting) so we can ensure the server will disregard anything coming from the phantom connection? I think this is needed to open the possibility for aggressive retries in low latency environments (or simply have control of our retry timings).
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/issues/673#issuecomment-375628062
########################################################################
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
