[jira] [Commented] (JCLOUDS-342) Consider handling 408 request timeout for retries

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCLOUDS-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918839#comment-13918839 ] 

ASF subversion and git services commented on JCLOUDS-342:
---------------------------------------------------------

Commit 9f11888f4bdf7f878c570bc76bdda2f81cd92fd4 in jclouds's branch refs/heads/master from Tom Manville
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=9f11888 ]

JCLOUDS-342: Retry on HTTP 408 for swift

To repro issue 342, the following steps were taken:
 - Spawn 500 parallel / 2000 total putBlobs to cloudfiles-uk
 - issue a SIGSTOP
 - wait 60 seconds
 - issue a SIGCONT

Without this patch, there are several hundred 408s.
With this patch, these are retried and complete successfully.


> Consider handling 408 request timeout for retries
> -------------------------------------------------
>
>                 Key: JCLOUDS-342
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-342
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-labs-openstack
>    Affects Versions: 1.7.0
>            Reporter: Andrew Gaul
>            Assignee: Thomas Manville
>             Fix For: 1.8.0, 1.7.2
>
>
> CloudFiles throws 408 Request Timeout errors for me occasionally and jclouds throws an HttpResponseException in reponse.  We should retry these like other transient errors in org.jclouds.openstack.swift.v1.handlers.SwiftErrorHandler.handleError.  clearContainer against large containers seems to surface these more often, perhaps due to high concurrency.



--
This message was sent by Atlassian JIRA
(v6.2#6252)