Skip to content

Conversation

@bbockelm
Copy link
Collaborator

Elsewhere, we use ETIME to indicate a server timeout (particularly, XRootD uses it for "504 Gateway Timeout"). Many users have found it confusing that timeouts result in "stale NFS file handle". Beyond giving the correct HTTP status code, this will cause the following message to be provided:

sTREAM ioctl timeout

It's not the greatest -- and the capitalization is strange -- but at least it includes the word "timeout". For the xroot protocol, one receives 3035, kXR_TimerExpired.

Elsewhere, we use ETIME to indicate a server timeout (particularly,
XRootD uses it for "504 Gateway Timeout").  Many users have found
it confusing that timeouts result in "stale NFS file handle".
Beyond giving the correct HTTP status code, this will cause the
following message to be provided:

```
sTREAM ioctl timeout
```

It's not the greatest -- and the capitalization is strange -- but
at least it includes the word "timeout".  For the xroot protocol,
one receives 3035, `kXR_TimerExpired`.
@bbockelm bbockelm requested a review from abh3 April 12, 2025 20:17
@amadio
Copy link
Member

amadio commented Apr 15, 2025

Looks good to me, let's hear from @abh3 before merging, though, since you asked for his review as well.

@amadio amadio moved this to Ready in Release Planning Apr 15, 2025
@amadio amadio moved this from Ready to In review in Release Planning Apr 15, 2025
@bbockelm
Copy link
Collaborator Author

Yup! Mostly wrote this down as a discussion point... if we agree it's an improvement, the patch itself is obviously trivial.

@bbockelm
Copy link
Collaborator Author

bbockelm commented May 8, 2025

@abh3 - this one is still waiting for your input. I understand @amadio would like to do a patch release soon and this would be a good opportunity.

@amadio amadio added this to the 5.8.2 milestone May 8, 2025
@amadio amadio merged commit e2cd33a into xrootd:master May 8, 2025
11 checks passed
@github-project-automation github-project-automation bot moved this from In review to Done in Release Planning May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants