Print

Print

New to 4.6.1, the client is no longer able recover after a socket error occurs. For an example of this, see the GGUS ticket referenced in #528.

It seems that this one is a bit more urgent, however: a variety of relatively-normal things can trigger a socket error (not necessarily a client problem as in #528 but day-to-day server failures and network hiccups).

The symptoms are as follows:

  1. Socket error occurs when talking to a data server.
  2. CMSSW performs a retry at the redirector.
  3. A timeout occurs on the file open.
  4. Callback is cleanly invoked, CMSSW returns a permanent error.

Prior to the 4.6.x upgrade, (3) never occurred. The xrootd client would be able to cleanly reopen the file and continue on.

Note: it occurred to me that around the time of the 4.6.x upgrade, read recovery was disabled in the client (as read recovery is also done in CMSSW). Is it possible that this is related to code paths that are only used if read recovery is disabled?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Client is unable to recover after socket error (#529)"}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/529"}}}

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