Implement timeouts for the Xrootd client. #5742
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The default timeout is now set to 10 minutes; previously, it varied
between 3 minutes and 8 hours, depending on the operation. Further,
the timeout can now be set by the CMSSW pset and the site local
config service.
It appears that timeouts were never set for fallback files;
this issue is now fixed.
Whenever a ReadV error occurs, raise a CMSSW exception; do not
allow this to be cast down to a ROOT warning. Exception information
is improved so the last Xrootd server message (or timeouts) are
recorded.
Finally, this fixes an older bug in XrdReadv.cc which causes the
transaction timeout to not be reset at the beginning of ReadV calls.
This causes the XrdAdaptor to throw an exception on ReadV
calls if it has been more than the timeout (default, 8 hours) between
Read calls (which did reset the transaction timeout).
This is a backport of PR #5714 per request from @davidlange6