[
https://issues.apache.org/jira/browse/AURORA-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127229#comment-14127229
]
Maxim Khutornenko commented on AURORA-693:
------------------------------------------
FWIW, based on irc discussion, this seems to be coming from our requests
implementation (TRequestsTransport) with the actual error pointing to:
requests/packages/urllib3/connectionpool.py
{noformat}
"INFO] Starting new HTTP connection (1): localhost"
{noformat}
{{1}} block might be responsible for retrying provided {{2}} has failed to
properly identify connection error in {{3}}
{{1}} -
https://github.com/kennethreitz/requests/blob/master/requests/packages/urllib3/connectionpool.py#L572-L579
{{2}} -
https://github.com/kennethreitz/requests/blob/master/requests/packages/urllib3/connectionpool.py#L558
{{3}} -
https://github.com/kennethreitz/requests/blob/master/requests/packages/urllib3/util/retry.py#L210-L269
> Aurora Client is pretty agressive when server answers with anything but 200
> ---------------------------------------------------------------------------
>
> Key: AURORA-693
> URL: https://issues.apache.org/jira/browse/AURORA-693
> Project: Aurora
> Issue Type: Bug
> Components: Client
> Reporter: alexius ludeman
>
> When using aurora client and scheduler responds with non-200, the client goes
> in a pretty tight infinite loop of retrying with the following message:
> INFO] Starting new HTTP connection (1): $hostname
> There are a few ways to reproduce:
> -invalid dns name
> -a port that responds with "Connect Refused"
> -server responds with non-200 (specifically 401)
> Some ways forward:
> - the client should try X many times, and give up.
> - sleep between requests.
> - log why it is failing
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
