You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Maxim Khutornenko (JIRA)" <ji...@apache.org> on 2014/08/01 04:00:40 UTC
[jira] [Resolved] (AURORA-629) Scheduler client does not retry
closed connection errors
[ https://issues.apache.org/jira/browse/AURORA-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Khutornenko resolved AURORA-629.
--------------------------------------
Resolution: Duplicate
Result of a flaky connection and jira retry button.
> Scheduler client does not retry closed connection errors
> --------------------------------------------------------
>
> Key: AURORA-629
> URL: https://issues.apache.org/jira/browse/AURORA-629
> Project: Aurora
> Issue Type: Bug
> Components: Client
> Reporter: Maxim Khutornenko
>
> This seems like a regression post https://reviews.apache.org/r/22274. Errors like this one are not retried anymore but rather caught and re-raised thus breaking update progress:
> {noformat}
> apache.aurora.client.api.scheduler_client.ThriftInternalError: Error during thrift call getTasksStatus to devcluster: (0, 'connection closed unexpectedly')
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)