Hi Marian,
Indeed this is a worrisome bug (more like not fully implemented). I
haven't been able to get anything from the developer. So, I would
recommend not using the throttle plugin until this gets straightened out.
At worst, xrdcp will crash when it encounters such a redirector. So,
nothing realy bad will happen but peoplewill know it is the case when it
does. As for throttle in server mode, it's problematic but not
devastating.
Andy
On Fri, 22 Jun 2018, Marian Zvada wrote:
> Ugh, from operation side I'd wonder whether we may have other redirectors in the federation configured similar way and causing basically redirect to data inaccessible (at least on those sites which enable throttle plugin). Hopefully, other site admins would have spotted it and shout or workflow users would have discovered it and complain, but that's hard to tell. Sure enough, this sounds like a critical bug to fix and in the meantime, we may ask sites to check their configuration on redirectors meantime. While in federation communication goes from top-level redirectors and users don't contact directly site managers, do you know @abh3 if the issue may be masked in the redirection chain if the throttle is set on-site manager or it doesn't really matter?
>
> --
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/752#issuecomment-399469209
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
{"@context":"http://schema.org","@type":"EmailMessage","potentialAction":{"@type":"ViewAction","target":"https://github.com/xrootd/xrootd/issues/752#issuecomment-399746772","url":"https://github.com/xrootd/xrootd/issues/752#issuecomment-399746772","name":"View Issue"},"description":"View this Issue on GitHub","publisher":{"@type":"Organization","name":"GitHub","url":"https://github.com"}}
{"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":"@abh3 in #752: Hi Marian,\n\nIndeed this is a worrisome bug (more like not fully implemented). I \nhaven't been able to get anything from the developer. So, I would \nrecommend not using the throttle plugin until this gets straightened out. \nAt worst, xrdcp will crash when it encounters such a redirector. So, \nnothing realy bad will happen but peoplewill know it is the case when it \ndoes. As for throttle in server mode, it's problematic but not \ndevastating.\n\nAndy\n\nOn Fri, 22 Jun 2018, Marian Zvada wrote:\n\n\u003e Ugh, from operation side I'd wonder whether we may have other redirectors in the federation configured similar way and causing basically redirect to data inaccessible (at least on those sites which enable throttle plugin). Hopefully, other site admins would have spotted it and shout or workflow users would have discovered it and complain, but that's hard to tell. Sure enough, this sounds like a critical bug to fix and in the meantime, we may ask sites to check their configuration on redirectors meantime. While in federation communication goes from top-level redirectors and users don't contact directly site managers, do you know @abh3 if the issue may be masked in the redirection chain if the throttle is set on-site manager or it doesn't really matter?\n\u003e\n\u003e -- \n\u003e You are receiving this because you were mentioned.\n\u003e Reply to this email directly or view it on GitHub:\n\u003e https://github.com/xrootd/xrootd/issues/752#issuecomment-399469209\n"}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/752#issuecomment-399746772"}}}
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [xrootd/xrootd] NULL pointer in XrdCl::XRootDMsgHandler? (#752)",
"sections": [
{
"text": "",
"activityTitle": "**Andrew Hanushevsky**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@abh3",
"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\": 752,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"xrootd/xrootd\",\n\"issueId\": 752\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/xrootd/xrootd/issues/752#issuecomment-399746772"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 348876614\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
