OK after discussions with Andy and Michal, the key piece of information I was missing is that the concepts of "Request" and "Stream" in SSI do not map to XRD_REQUESTTIMEOUT and XRD_STREAMTIMEOUT.
- XRD_STREAMTIMEOUT is suppressed by the XRootD server when it receives a SSI request (sends respwait)
- XRD_REQUESTTIMEOUT controls both the time for the SSI Request and each packet of the SSI Stream
This could be made clear in the documentation.
For the case of independently controlling the the timeout for obtaining the stream handle and the timeout for obtaining a chunk of data from the stream, it seems this is possible by changing the Request timeout (which can be set on a per-request basis) after the stream handle is received.
An alternative would be to allow the server to set the waitresp time.
Anyway for now I think we understand how it works and have enough to do what we need.
—
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://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@slithy in #829: OK after discussions with Andy and Michal, the key piece of information I was missing is that the concepts of \"Request\" and \"Stream\" in SSI do not map to XRD_REQUESTTIMEOUT and XRD_STREAMTIMEOUT.\r\n\r\n* XRD_STREAMTIMEOUT is suppressed by the XRootD server when it receives a SSI request (sends respwait)\r\n* XRD_REQUESTTIMEOUT controls both the time for the SSI Request and each packet of the SSI Stream\r\n\r\nThis could be made clear in the documentation.\r\n\r\nFor the case of independently controlling the the timeout for obtaining the stream handle and the timeout for obtaining a chunk of data from the stream, it seems this is possible by changing the Request timeout (which can be set on a per-request basis) after the stream handle is received.\r\n\r\nAn alternative would be to allow the server to set the waitresp time.\r\n\r\nAnyway for now I think we understand how it works and have enough to do what we need."}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/829#issuecomment-429331609"}}}
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/829#issuecomment-429331609",
"url": "https://github.com/xrootd/xrootd/issues/829#issuecomment-429331609",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
},
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [xrootd/xrootd] [SSI] Problems with timeouts during SSI streaming (#829)",
"sections": [
{
"text": "",
"activityTitle": "**Michael**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@slithy",
"facts": [
]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"xrootd/xrootd\",\n\"issueId\": 829,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}"
}
]
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/xrootd/xrootd/issues/829#issuecomment-429331609"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 383855100\n}"
}
],
"themeColor": "26292E"
}
]
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