Print

Print

This is thought to solve a XrdCl hang: an XrdCl synchronous call waiting for the callback apparently indefinitely. (This issue has entry EOS-4323 the EOS tracker). The problem was seen to be associated with a network glitch on the service machines hanging a messaging thread which uses XrdCl.

The flow is believed to be that ReOpenFileAtServer() returns an error, e.g. due to DNS name lookup failure. RunRecover() then sets the FileStateHandler's pFileState = Error, but sets no error in pStatus. The Error state causes subsequent calls like FileStateHandler::Close() or Stat() etc. to fail by returning the status contained in pStatus. In this cases pStatus still contains an OK status. Thus the client waits forever for a response that never comes, as it was never submitted nor failed at submission time.

The above has been reproduced in a test program with forced network problems; but not from with EOS code.

You can view, comment on, or merge this pull request online at:

  https://github.com/xrootd/xrootd/pull/1723

Commit Summary

File Changes

(1 file)

Patch Links:

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/pull/1723@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/pull/1723", "url": "https://github.com/xrootd/xrootd/pull/1723", "name": "View Pull Request" }, "description": "View this Pull Request 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